CVE-2025-36897
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 · uneditedIn unknown of cd_CnMsgCodecUserApi.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
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 out-of-bounds write vulnerability exists in cd_CnMsgCodecUserApi.cpp due to a missing bounds check before a memory write operation. This memory corruption flaw can be exploited remotely to achieve code execution without requiring any privileges or user interaction, as indicated by the critical CVSS score.
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 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 vulnerable cd_CnMsgCodecUserApi componentSearch the device filesystem for the file cd_CnMsgCodecUserApi.cpp or its compiled binary (typically in /system/lib or vendor partitions). Use 'find /system -name *CodecUserApi*' or check for libraries containing 'CodecUserApi' in their metadata.Affected if The component cd_CnMsgCodecUserApi.cpp or its compiled binary exists on the device, indicating the vulnerable code path is present.
-
Determine if the codec user API is exposedCheck if the device runs a media codec service that processes codec messages. Look for processes or services related to media codec handling (often via 'ps -A' or '/vendor/etc/init' scripts).Affected if A media codec service or daemon that utilizes the cd_CnMsgCodecUserApi component is running on the device.
-
Check for the presence of the affected binary in system librariesExamine /system/lib64/ or /vendor/lib64/ for shared objects (.so files) that may contain the codec user API logic. Use 'ls -la' to list codec-related libraries.Affected if Compiled binaries or libraries implementing the codec user API are present in the system or vendor partitions.
-
Verify Android version as secondary confirmationRun 'getprop ro.build.version.release' or check Settings > About Phone to confirm the Android version. Even though all versions are affected, document the version for triage purposes.Affected if The device is running any version of Google Android.
If the cd_CnMsgCodecUserApi component or its compiled binary is present on the Android device, the environment is affected by this vulnerability since all Android versions contain the missing bounds check in the codec user API code path.
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 dataApply vendor-supplied patches for the affected component and conduct a code audit of cd_CnMsgCodecUserApi.cpp to implement proper bounds validation before all buffer write operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36897 — 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-36897 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