C2paApplication · Adobe
CVE-2026-34680
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 · uneditedCAI Content Credentials versions [email protected], c2pa-v0.78.2 and earlier are affected by an Integer Overflow or Wraparound vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. Exploitation of this issue does not require user interaction.
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 confidenceInteger overflow vulnerability in CAI Content Credentials libraries (c2pa-web and c2pa-v) allows unauthenticated attackers to crash applications via the vulnerable code path, causing denial-of-service without user interaction.
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
C2paApplication
< 0.80.1< 0.7.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Adobe C2pa (c2pa-v) library versionLocate the c2pa-v or c2pa library in your environment (check package.json, node_modules, Cargo.toml, vendor directories, or application dependencies) and retrieve the installed version numberAffected if The installed version is below 0.80.1
-
Identify installed Adobe C2pa Web (c2pa-web) library versionLocate the c2pa-web library in your environment (check package.json, node_modules, or web application dependencies) and retrieve the installed version numberAffected if The installed version is below 0.7.1
-
Determine if affected libraries are actively loadedInspect your application runtime or build configuration to confirm whether c2pa-v or c2pa-web libraries are being loaded or used at runtimeAffected if Either library is loaded and the version falls within the affected ranges
Your environment is affected if Adobe C2pa (c2pa-v) below version 0.80.1 or Adobe C2pa Web (c2pa-web) below version 0.7.1 is installed and actively used by your application.
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 · scoped0.7.10.80.1
Upgrade c2pa-web to version greater than 0.7.0 and c2pa-v to version greater than 0.78.2 to obtain patched versions that address the integer overflow.
C2pa >= 0.80.1, C2pa Web >= 0.7.1
- Identify which C2pa package is in use (c2pa for the SDK or c2pa-web for web integration)
- Check current installed version using package manager (e.g., npm list c2pa or npm list c2pa-web)
- Upgrade c2pa package to version 0.80.1 or later: npm install c2pa@^0.80.1
- Upgrade c2pa-web package to version 0.7.1 or later: npm install c2pa-web@^0.7.1
- Verify the upgrade completed successfully and test the application to ensure functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in C2pa
Scoped from the published advisory
- 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-2026-34680 — 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-34680 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