CVE-2025-68114
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 · uneditedCapstone is a disassembly framework. In versions 6.0.0-Alpha5 and prior, an unchecked vsnprintf return in SStream_concat lets a malicious cs_opt_mem.vsnprintf drive SStream’s index negative or past the end, leading to a stack buffer underflow/overflow when the next write occurs. Commit 2c7797182a1618be12017d7d41e0b6581d5d529e fixes the issue.
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 confidenceA buffer underflow/overflow vulnerability exists in Capstone's SStream_concat function where an unchecked return value from vsnprintf allows a malicious custom cs_opt_mem.vsnprintf handler to manipulate the stream's internal index to negative or past the buffer end, causing stack buffer corruption on subsequent writes.
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< 6.0.0= 6.0.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
- 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 installed Capstone versionRun 'capstone --version' or check the library file version (e.g., libcapstone.so.X) in your installation directory. Compare against affected versions: < 6.0.0 or = 6.0.0Affected if Version is less than 6.0.0 or exactly 6.0.0
-
Locate the SStream_concat function usageSearch your codebase or Capstone binary for references to SStream_concat function. This is the vulnerable function where the unchecked vsnprintf return value occurs.Affected if Your application or integrated Capstone uses SStream_concat for string concatenation in the disassembly engine
-
Check for custom vsnprintf handler configurationInspect your code for cs_opt_mem structure initialization, specifically looking for a custom vsnprintf function pointer assignment to cs_opt_mem.vsnprintf. This handler, if malicious or compromised, can trigger the vulnerability.Affected if A custom cs_opt_mem.vsnprintf handler is registered and being used by Capstone
-
Verify stream index manipulation is possibleIf using a custom vsnprintf handler, verify whether it can return values that would cause the stream's internal index to become negative or exceed buffer boundaries before SStream_concat writes to the buffer.Affected if The custom vsnprintf handler can return values outside the expected return range, causing buffer underflow/overflow in subsequent writes
You are affected if your Capstone version is < 6.0.0 or = 6.0.0 AND your code uses SStream_concat with a custom cs_opt_mem.vsnprintf handler that can manipulate the stream index to invalid values.
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 · scoped6.0.0
Upgrade to a version beyond the fixed commit (2c7797182a1618be12017d7d41e0b6581d5d529e) or apply the commit's fix to add proper bounds checking on the vsnprintf return value.
Capstone 6.0.1 or later
- 1. Identify the current version of Capstone in use by checking project dependencies or build files
- 2. Upgrade Capstone to version 6.0.1 or later which contains the security fix for the SStream_concat buffer overflow vulnerability
- 3. If using a package manager (pip, conan, brew, etc.), update the dependency: for pip use 'pip install --upgrade capstone', for conan update the recipe version
- 4. Rebuild and test the application to ensure the upgrade does not introduce regressions
- 5. Verify the new version is running: import capstone; print(capstone.__version__)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.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 $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68114 — 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-68114 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