Claude Discovers Vulnerabilities Across 16 SAML Projects in One Month, Exposing Maintenance Gaps
Security researcher Eric Chiang, CTO of Oblique Security, used Anthropic's Claude Opus model to uncover vulnerabilities in 16 SAML implementations during approximately one month of evening work. The project was conducted under the Anthropic Cyber Verification Program, which removed safety restrictions and allowed the model to generate working exploits.
Four complete authentication bypasses were found in Authentik, the PHP library lightsaml, the OneUptime platform, and the Java project saml-client. An additional twelve projects proved vulnerable to signature bypasses on secondary protocol messages such as AuthnRequest, AttributeQuery, and LogoutRequest, enabling data disclosure and forced session termination. Several libraries were also driven into denial-of-service conditions through unauthenticated XML POST requests that exhausted memory.
The most prominent single issue was CVE-2026-57580 in Authentik, independently reported by eight researchers. The flaw allowed an attacker to insert an XML comment into the NameID field, truncate the value to an attacker-controlled address, and maintain a valid signature under non-default account mapping configurations. The vulnerability was fixed in versions 2026.2.6 and 2026.5.5.
Chiang's pipeline operated in two phases. The first phase used agents to locate behavioral anomalies, or "gadgets," across SAML libraries. The second phase combined these gadgets into end-to-end exploits. Intermediate results were stored in JSONL files, and a deduplication step discarded out-of-scope findings before expensive verification tokens were spent. No specialized training on past SAML vulnerabilities was required; providing historical examples actually reduced the model's effectiveness by encouraging it to search only for known patterns.
Reporting the findings proved more difficult than discovering them. The OneUptime project initially ignored the private report, then merged large pull requests generated without human review that Chiang subsequently broke. Three rounds of fixes were ultimately needed. Other maintainers either failed to respond or were overwhelmed by the volume of AI-generated reports, with one company requesting screen recordings to filter automated submissions.
Chiang, who previously added SAML support to the Dex project nearly a decade ago, has long argued that the protocol is inherently fragile due to the separation between signature verification libraries and application logic. He was unable to break the core protocol itself in mature implementations and recommends that organizations avoid writing custom SAML code, preferring established libraries or migrating to OpenID Connect.
Related articles
Recon in Bug Bounty: Spotting Anomalies Instead of Chasing Known Vulnerability Patterns
The article explains that effective reconnaissance in Bug Bounty programs goes far beyond automated subdomain enumeration with tools like subfinder or httpx. It emphasizes building a mental model of the target application by analyzing policy documents, infrastructure changes via Censys and Shodan, and identifying behavioral anomalies rather than matching textbook vulnerability patterns. A detailed case study describes how a hidden legacy endpoint on ibm.com was discovered during passive and active reconnaissance, leading to the identification of a time-based Blind SQL Injection vulnerability confirmed with sqlmap. The author stresses that recon is a continuous process involving hypothesis testing, understanding service trust boundaries, and evaluating real security impact for triage teams. Practical advice includes reviewing HackerOne reports for context, maintaining motivation through interesting targets, and revisiting programs as infrastructure evolves. The piece also covers how JavaScript analysis and direct endpoint interaction help map authorization flows and weak links between microservices.
Google Releases Chrome Security Update Fixing 32 Vulnerabilities Including One Critical Flaw
Google has issued a security update for its Chrome browser that addresses a total of 32 vulnerabilities across Windows, macOS, and Linux platforms. One vulnerability is rated Critical, while 25 are rated High, one Medium, and five Low. The Critical issue, tracked as CVE-2026-102331, is a buffer overflow in the ANGLE graphics component that was reported externally on August 24. High-severity fixes cover multiple type confusion and buffer overflow problems in the V8 JavaScript engine, use-after-free flaws in Bluetooth, Views, Passwords, FullScreen, and PictureInPicture, plus uninitialized resource handling in GPU and WebGPU. Additional High issues include out-of-bounds writes in GPU, out-of-bounds reads in WebGL, cross-site scripting in WebUI, UI display problems in Omnibox, and permission management weaknesses in Mojo. The update ships as Chrome 154.0.8037.93 and 154.0.8037.92 for Windows and macOS and 154.0.8037.92 for Linux, with gradual rollout over the coming days and weeks.
Automated Scans Exploit CVE-2026-39364 in Exposed Vite Dev Servers to Steal AWS and Azure Secrets
A large-scale automated campaign is actively scanning the internet for publicly exposed Vite development servers to exfiltrate sensitive files and cloud credentials. Attackers leverage CVE-2026-39364 to bypass server.fs.deny restrictions and read arbitrary files using crafted query parameters such as ?raw combined with ?import. The campaign has generated thousands of requests over several weeks, with telemetry from honeypots recording 807 sessions and roughly 32,000 events in a single month. Targets include .env files, terraform.tfstate, and other infrastructure-as-code artifacts that often contain AWS access keys and Microsoft Azure tokens. The vulnerable versions are Vite 7.1.0 through versions prior to 7.3.2 and Vite 8.x prior to 8.0.5. Part of the scanning traffic originates from Google Cloud IP ranges 34.x and 35.x. Organizations are urged to update immediately, restrict the dev server to localhost, and rotate any exposed cloud credentials.
cKEV Index Launches to Prioritize Vulnerabilities Using Urgent Patch Score Methodology
CyberOK has introduced the open cKEV Index, a catalog of high-priority vulnerabilities based on the Urgent Patch Score (UPS) framework that tracks signals such as exploit publication and confirmed attacks. The index addresses the growing gap between accelerated vulnerability discovery powered by AI and the slower pace of patching, testing, and deployment in real environments. It incorporates timelines from sources including Anthropic reports on AI-assisted campaigns GTG-50014 and GTG-50029, the rust-in-peace framework, Microsoft Exchange Server Subscription Edition delays, and Oracle’s record 1,434 CVE fixes. UPS defines progressive phases from Radar to Emergency/IR, allowing teams to link specific events like PoC releases or CISA KEV additions to concrete actions under resource constraints. Research using 2025 CISA KEV data shows that early signals enable 35–53% of patches to be completed before official exploitation confirmation. The public version displays only Urgent Patch and Emergency stages with event histories, while full data and API access are available to CyberOK customers.