Authentication bypass via encrypted unsigned SAML assertions
Published Jun 11, 2026 · Updated Jun 11, 2026
Improper SAML signature verification in Cloud Foundry UAA 2.0.0 through 78.13.0 allows remote attackers to impersonate users. The token endpoint and ACS accept encrypted assertions or responses without proving that a trusted IdP signed them, even though any party can encrypt data with the published SP key. No prior authentication is required; browser SSO additionally requires wantAssertionSigned to be false, and acceptance grants the forged identity's access.
Summary
What happened
Improper SAML signature verification in Cloud Foundry UAA 2.0.0 through 78.13.0 allows remote attackers to impersonate users. The token endpoint and ACS accept encrypted assertions or responses without proving that a trusted IdP signed them, even though any party can encrypt data with the published SP key. No prior authentication is required; browser SSO additionally requires wantAssertionSigned to be false, and acceptance grants the forged identity's access.
The record
- CVE
- CVE-2026-41005
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Cloud Foundry Foundation
- Product
- cf-deployment
- Classifications
- CWE-347, CAPEC-475, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0 <57.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo