dbcve.org
C2paApplication · Adobe

CVE-2026-34688

MEDIUM · 6.2 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 0.7.1 / 0.80.1 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
CAI Content Credentials versions [email protected], c2pa-v0.78.2 and earlier are affected by an Improper Input Validation 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 confidence

The CAI Content Credentials libraries (c2pa-web and c2pa-v) contain an improper input validation vulnerability that allows attackers to crash the application via malformed input without any user interaction, leading to denial-of-service.

MitigationUpgrade to c2pa-web version greater than 0.7.0 and c2pa-v version greater than 0.78.2 to obtain the patched versions addressing the input validation flaw.

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
Affected:< 0.80.1
C2pa WebApplication
Affected:< 0.7.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify which C2pa library is in use
    Review your project's dependencies (package.json, Cargo.toml, pom.xml, or similar) to find references to 'c2pa-v', 'c2pa-web', '@adobe/c2pa', or similar Adobe Content Credentials packages
    Affected if Any of these libraries are present in the project dependencies
  2. Check installed version of c2pa-v library
    Run 'npm list c2pa-v' for Node.js projects, or inspect the lock file (package-lock.json, yarn.lock) for the installed version. For Rust projects, check Cargo.lock for the c2pa-v crate version
    Affected if The installed version is present and is less than 0.80.1
  3. Check installed version of c2pa-web library
    Run 'npm list c2pa-web' for Node.js projects, or inspect the lock file for the installed version
    Affected if The installed version is present and is less than 0.7.1
  4. Verify Adobe C2pa package version
    Run 'npm list @adobe/c2pa' or inspect package.json to identify if the main Adobe C2pa package is in use, then check its version against the affected range
    Affected if The package version is present and is less than 0.80.1

Your environment is affected if you have c2pa-v versions below 0.80.1 or c2pa-web versions below 0.7.1 installed, as these contain the vulnerable input validation code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.7.1 / 0.80.1 or later
Fixed in 0.7.10.80.1
Interim mitigation

Upgrade to c2pa-web version greater than 0.7.0 and c2pa-v version greater than 0.78.2 to obtain the patched versions addressing the input validation flaw.

Recommended fix High confidence

C2pa: upgrade to 0.80.1 or later | C2pa Web: upgrade to 0.7.1 or later

  1. Identify which C2pa library is in use (c2pa or c2pa-web)
  2. For C2pa (JavaScript/Node.js): Run 'npm install [email protected]' or update the version in package.json to ^0.80.1 and run 'npm install'
  3. For C2pa Web: Run 'npm install [email protected]' or update the version in package.json to ^0.7.1 and run 'npm install'
  4. Verify the installed version matches the fixed release using 'npm list c2pa' or 'npm list c2pa-web'
  5. Rebuild and redeploy the application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in C2pa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34688 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34688 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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