Skip to main content
VulnerabilityPublished Updated

CVE-2026-41005: Cloud Foundry UAA · Improper Verification of Cryptographic Signature

Affects Cloud Foundry UAASource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.0 Critical : upgrade to 78.14.0 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 78.14.0, 57.0.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade UAA to 78.14.0; CF Deployment to 57.0.0.

Affected software

ProductAffectedFixed in
Cloud FoundryUAAAffected
  • >=2.0.0 <78.14.0
Fixed in
  • 78.14.0
Cloud FoundryCF DeploymentAffected
  • <57.0.0
Fixed in
  • 57.0.0

AI-suggested

If you cannot patch yet, users should consider enforcing wantAssertionSigned=true in SAML configurations to require signed assertions and responses, thereby mitigating the risk of accepting unsigned encrypted content.

Description

Cloud Foundry UAA incorrectly treated XML encryption to the Service Provider (confidentiality) as a substitute for XML signatures from the Identity Provider (authenticity) in two SAML flows: the OAuth 2.0 SAML2 bearer grant (token endpoint) and browser SSO (ACS) when wantAssertionSigned is set to false. Assertions or responses that were unsigned but contained encrypted content could still be accepted. Encryption uses the SP's public key from published metadata, therefore, any party, not only a trusted IdP, can produce ciphertext UAA can decrypt; successful decryption therefore does not prove the IdP issued the message. Affected versions: Cloud Foundry UAA (uaa_release) 2.0.0 through 78.13.0. Cloud Foundry CF Deployment all versions through 56.1.0.

References

Community reviews

Loading reviews…