CVE-2026-14787
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 · uneditedA weakness has been identified in radareorg radare2 up to 6.1.6. Affected is the function cmd_print in the library libr/core/cmd_print.inc of the component pb Print Command Handler. This manipulation causes integer overflow. The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. Patch name: 2b6265476c75567006b0fcbb749f4ae7b189c5df. It is recommended to apply a patch to fix this 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 confidenceInteger overflow vulnerability in radare2's pb Print Command Handler (cmd_print function in libr/core/cmd_print.inc) allows local attackers to cause heap corruption or potentially achieve code execution via specially crafted input. The vulnerability exists up to version 6.1.6 and requires local access for exploitation.
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.1.0, <= 6.1.6CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify radare2 is installedRun 'which r2' or 'r2 -v' to confirm radare2 is present on the systemAffected if radare2 is not found on the system, then this CVE does not apply
-
Determine installed radare2 versionRun 'r2 -v' to retrieve the exact version number of the installed radare2 binaryAffected if The version displayed is between 6.1.0 and 6.1.6 inclusive, indicating the affected range
-
Confirm version falls within affected rangeCompare the retrieved version against the affected range: versions 6.1.0 through 6.1.6 are vulnerableAffected if Installed version is 6.1.0, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, or 6.1.6
A system is affected if radare2 is installed and the version is 6.1.0 through 6.1.6, as the integer overflow in the pb Print Command Handler exists only in these versions.
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 · scopedApply the provided patch (commit 2b6265476c75567006b0fcbb749f4ae7b189c5df) to fix the integer overflow in cmd_print, or upgrade to radare2 version 6.1.7 or later which contains the security fix.
6.1.7 or later (next stable release after 6.1.6)
- 1. Identify the current installed version of radare2 using: r2 -v or radare2 -v
- 2. If version is between 6.1.0 and 6.1.6 inclusive, plan for upgrade
- 3. Clone or pull the latest radare2 repository: git clone https://github.com/radareorg/radare2
- 4. Navigate to the radare2 directory
- 5. Run sys/install.sh to build and install the latest version
- 6. Alternatively, use system package manager to upgrade if a newer package is available
- 7. Verify the upgrade was successful by running: r2 -v
- 8. Test that the pb print command functionality works correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14787 — 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-2026-14787 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