CVE-2025-21472
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 · uneditedInformation disclosure while capturing logs as eSE debug messages are logged.
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 · moderate confidenceAn information disclosure vulnerability exists where eSE (embedded Secure Element) debug messages are being captured in logs, potentially exposing sensitive information that should not be visible.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 the Qualcomm firmware in useCheck system documentation, firmware version, or device specifications to determine if the system uses Fastconnect 6900, Fastconnect 7800, Qca9367, Qca9377, Qcs8550, Sa8530p, Sa8540p, or Sa9000p firmware.Affected if The system uses any of the listed Qualcomm firmware products.
-
Locate eSE debug logging configurationSearch system configuration files, firmware settings, or diagnostic menus for options related to eSE (embedded Secure Element) debug logging, trace logging, or verbose logging. Look for settings like 'eSE debug', 'SE debug', 'secure element logging', or similar.Affected if eSE debug logging is enabled or configurable in the system.
-
Examine system log files for eSE messagesReview system log files (such as debug logs, system logs, kernel logs, or vendor-specific diagnostic logs) for entries containing keywords like 'eSE', 'secure element', 'SE', 'embedded Secure Element', or related debug labels.Affected if Log files contain any eSE or Secure Element related messages.
-
Inspect eSE log content for sensitive dataAnalyze any eSE-related log entries found for the presence of sensitive information such as cryptographic keys, tokens, authentication data, PINs, or other secure element data that should not be exposed in plain text.Affected if Log entries contain sensitive information from the embedded Secure Element in plain text.
The user is affected if their system uses any of the listed Qualcomm firmware products and eSE debug messages with sensitive data are present in their logs.
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.
From vendor dataDisable or remove eSE debug message logging in production environments, or ensure logs containing such messages are properly sanitized/redacted before storage or review.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21472 — 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-21472 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