FFmpeg fixes PixelSmash flaw in widely used video decoder

sbom-cve-check 1.4.0 released

sbom-cve-check 1.4.0 has been released, adding an OpenVEX exporter and improving Linux kernel CVE analysis and version parsing. The new openvex export type, contributed by Andrey Zhizhikin, generates OpenVEX v0.2.0 documents with VEX assessments, configurable via a new --export-author option. Kernel CVE handling now distinguishes mainline versions like 6.12 from stable versions like 6.12.34 to reduce false positives and negatives. Version parsing also gained support for formats like 0.9~rc5 and Ubuntu-style suffixes, and build metadata like 1.25.0+4f85853f64 is now ignored per semver rules. Install or upgrade with pip install --upgrade "sbom-cve-check[extra]".

Red Flags to Watch for When Choosing Between AI Pentesting Vendors

Choosing between AI pentesting vendors requires looking past marketing labels like 'autonomous' or 'agentic' because the underlying systems vary widely. A Stanford-led study ran different AI agent frameworks against a live 8,000-host network and found that between 55% and 82% of reported findings were confirmed as real vulnerabilities. Swapping only the underlying model moved one framework's valid finding rate from 57% to 80%, yet that same framework still scored lowest overall since its findings stayed shallow. On a CTF-style benchmark two frameworks scored near-identically (48.6% vs 45.9%), but on the live network one scored nearly three times higher on severity and complexity. Buyers should demand proof of exploitation, real-network results, clear safety controls, data handling answers and clarity on what 'continuous' actually means.

N-able takes cloud platform offline after 30+ "zero-days" published

N-able has taken its hosted N-central environments offline and urged on-premises customers to shut down their servers after a security researcher publicly disclosed more than 30 alleged zero-day vulnerabilities, including exploits that could let attackers take over vulnerable systems.

Learn Real-World Penetration Testing: Hands-On Ethical Hacking Crash Course

Understanding how malicious actors infiltrate networks is the first step to building resilient infrastructure. To help developers and aspiring security analysts learn the fundamentals of offensive sec

Pwn.college

pwn.college is a free, hands-on education platform for learning core cybersecurity and hacking skills, maintained by a team at Arizona State University. Learners progress through belt ranks, starting with a 'white belt' and earning belts through practice. Hackers continue beyond the platform to 'brown belt' and eventually 'black belt' status, which must happen outside the dojo. The site powers much of ASU's cybersecurity curriculum and asks users not to post writeups or walkthrough videos of challenge solutions. It points learners toward CTFtime.org for Capture The Flag events and a GitHub list of wargames for further practice. The underlying infrastructure is open source and accepts pull requests, though some modules remain closed-source.

Who Gives A Crap? Hackers, apparently, after toilet paper maker's customer data exposed

UK shoppers caught up in third-party security mess, and nobody knows whether the data was flushed away

AI in Production Without a WHERE Clause

Bối cảnh triển khai AI mà không có bước review rủi ro giống như thiếu một WHERE clause trong SQL có thể dẫn đến đêm dài khắc phục sự cố. Nguyên nhân kỹ thuật nằm ở việc các model AI có thể tạo ra dữ liệu không mong muốn khi không có bộ lọc phù hợp. Hệ quả có thể rất nghiêm trọng khi hệ thống AI vô tình tạo ra nội dung độc hại, sai lệch hoặc vi phạm chính sách. Đáng học hỏi là bài nhấn mạnh việc xác định rõ vị trí của cơ chế "phanh" (brake) trong hệ thống AI và ai chịu trách nhiệm kiểm soát nó.

Bài viết này giải thích tại sao thiếu bước kiểm duyệt trong AI sản xuất có thể dẫn đến hậu quả nghiêm trọng như lỗi query SQL không có WHERE clause.

Video Encoding for the Web in 2026: Part 2: Methodology and Tooling

This is Part 2; see Part 1 for an introduction. Methodology My big goal here is to be able to repeatably measure how well various video encoder settings work against the types of videos that I care about. In 2025, I took a single 1080p test video1Included as deception1, below. and ran around a thousand tests against it to see how well various H.265 encoding options worked. This time, I wanted to test against multiple videos and multiple encoders to get a much wider view of encoding performance. Before I started this, I wanted to improve my tooling so I wasn’t wasting time or measuring the wrong thing.