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
CISA Adds BeyondTrust Remote Support and Fortinet Flaws to KEV Catalog Following Zero-Day Exploitation by ARMORY CASTLE
The US Cybersecurity and Infrastructure Security Agency has added two vulnerabilities affecting Fortinet and BeyondTrust products to its Known Exploited Vulnerabilities catalog. CVE-2026-102764 is an authentication bypass flaw in BeyondTrust Remote Support that allows remote attackers to manipulate appliance files without credentials due to insufficient source validation. BeyondTrust released an advisory on October 15, 2026, rating the issue 9.3 on CVSS v4.0 as Critical. Mandiant attributes the zero-day exploitation to the suspected Chinese group ARMORY CASTLE, which deployed web shells for persistence and privilege escalation in late August. The second CVE, CVE-2025-61624, also appears on the KEV list but lacks further public technical details in the current advisory. Organizations are urged to apply patches immediately to prevent further compromise.
Use-After-Free in HTTP/2 Upload Leads to Potential RCE in curl: Detailed Analysis of CVE-2026-92392
In curl 8.23.0, developers fixed a high-severity Use-After-Free vulnerability tracked as CVE-2026-92392 that could allow remote code execution during HTTP/2 uploads. The flaw stems from a dangling pointer left on an easy handle after a server resets an HTTP/2 stream, which later gets dereferenced when the multi handle closes. An attacker controlling the server can influence memory contents to hijack a function pointer and execute arbitrary code, though successful exploitation requires precise conditions including upload size, memory layout, and knowledge of the target architecture. The issue was discovered by Luna Tong at Anthropic using their OSS Scanner and reported to the curl security team on September 15. The team accelerated the release cycle by two weeks to deliver the fix while maintaining standard procedures. curl maintainers continue reducing internal handle pointers in favor of identifiers and are adding more tests and static analysis to prevent similar memory-safety errors. The vulnerability highlights ongoing risks in C-based networking code handling multiplexed protocols like HTTP/2.
Automating Asset Scanning in MaxPatrol VM via API: Part 4 on Authentication
A detailed technical guide explains how to build asset scanning automation in MaxPatrol VM using its API, starting with authentication methods. The author covers three authorization options including local account login-password, domain account credentials, and reference tokens, providing working Python examples for local accounts. Code reads secrets from an .env file and obtains a Bearer token valid for 24 hours from the Core role instance. The post details required privileges in both the Management Console and MaxPatrol 10 for tasks such as vulnerability exports, dynamic asset group management, scan task creation, and report exporting. It credits Alexey Leonov for an early GitHub script that enabled practical API usage and lists additional resources including webinars, SDK, CLI, Jira integration, and a Postman collection. All subsequent API calls rely on the generated headers containing the Bearer token.
Securing Hadoop Clusters: Removing Passwords from XML Configs with Credential Provider API and JCEKS
Hadoop configurations frequently expose sensitive credentials such as database passwords and cloud access keys in plain text within files like hive-site.xml and core-site.xml. The Credential Provider API, introduced in Hadoop 2.6, allows applications to retrieve secrets from an external JCEKS keystore instead of embedding them directly in XML. This mechanism uses conf.getPassword() to fetch decrypted values from the keystore when hadoop.security.credential.provider.path is configured. JCEKS relies on the outdated PBEWithMD5AndTripleDES algorithm, which remains vulnerable to Sweet32 attacks in theory though practical risk for small keystore files is low. Master password protection for the keystore itself is the weakest link, with options including environment variables, protected password files, or HDFS Transparent Data Encryption. Arenadata has automated credential encryption management in its ADH platform through ADCM to handle keystore creation, permission setting, and rotation across cluster nodes.