CVE-2025-22246
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCloud Foundry UAA release versions from v77.21.0 to v7.31.0 are vulnerable to a private key exposure in logs.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCloud Foundry UAA (User Account and Authentication) releases v77.21.0 through v7.31.0 contain a vulnerability where private keys are being written to log files. This is an information disclosure issue where sensitive cryptographic material intended to remain secret is exposed in plaintext logs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 45.1.0, < 49.0.0>= 77.21.0, < 77.32.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed UAA versionRun 'uaac version' or check the UAA release manifest file in your deployment (usually in /uaa-release or via 'bosh vms -d uaa'). Compare the version number against the affected range: >= 77.21.0 and < 77.32.0 for UAA Release, or >= 45.1.0 and < 49.0.0 for CF Deployment.Affected if The installed UAA version falls within v77.21.0 through v77.31.0 (or CF Deployment between 45.1.0 and 48.x)
-
Locate UAA log filesFind the UAA log directory - typically at /var/vcap/sys/log/uaa/ or check the deployment manifest for the 'log_dir' property. Common log files include 'uaa.log', 'audit.log', or files under the configured logging path.Affected if Log files exist and are accessible (default UAA installations)
-
Search log files for private key patternsUse grep or a text search to scan UAA log files for PEM private key headers: look for strings like '-----BEGIN RSA PRIVATE KEY-----', '-----BEGIN PRIVATE KEY-----', '-----BEGIN EC PRIVATE KEY-----', or the string 'ssh-rsa' appearing in logs.Affected if Any of these private key patterns are found in plaintext within the log files
-
Check UAA audit logs for cryptographic operationsExamine the UAA audit.log (typically at /var/vcap/sys/log/uaa/audit.log) for events related to key generation, token signing, or SAML operations that may have logged sensitive material.Affected if Audit logs contain entries with exposed private key material
-
Verify OIDC or SAML identity provider configurationIf UAA is configured as an OIDC provider or SAML Service Provider, check the UAA logs around the time of identity provider metadata import or key rotation events, as these operations can trigger the vulnerable logging.Affected if OIDC or SAML identity providers are configured and were active during the affected version timeframe
A user is affected if their UAA version is between v77.21.0 and v77.31.0 (or CF Deployment between 45.1.0 and 49.0.0) AND any plaintext private key material is found in their UAA log files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped49.0.077.32.0
Upgrade UAA to the latest patched version beyond v7.31.0, rotate all exposed private keys, and audit log files for any private key exposure.
Cf Deployment >= 49.0.0, UAA Release >= 77.32.0
- Upgrade Cf Deployment to version 49.0.0 or later
- Upgrade UAA Release to version 77.32.0 or later
- After upgrade, verify that logs no longer contain private key information
- Audit existing logs for any potential private key exposure and rotate keys if necessary
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data