dbcve.org
C2paApplication · Adobe

CVE-2026-34668

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

CAI Content Credentials libraries ([email protected] and c2pa-v0.78.2 and earlier) contain an improper input validation vulnerability that allows an attacker to crash the application via crafted input, resulting in denial-of-service without requiring user interaction.

MitigationUpdate to a patched version of c2pa-web and c2pa-v libraries once available; until then, implement input validation and bounds checking on data processed by these libraries to prevent crash-inducing inputs.

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 c2pa-web library usage
    Locate and inspect the c2pa-web package installation in your project dependencies (e.g., check package.json, package-lock.json, or node_modules/c2pa-web/package.json) and note the installed version number
    Affected if the installed version is below 0.7.1 (such as 0.7.0 or earlier)
  2. Identify c2pa-v library usage
    Locate and inspect the c2pa-v package installation in your project dependencies (e.g., check package.json, package-lock.json, node_modules/c2pa-v/package.json, or Cargo.toml if using Rust) and note the installed version number
    Affected if the installed version is at or below 0.78.2 (including any 0.78.x patch version)
  3. Check for Adobe C2pa library usage
    Identify if your application uses the Adobe C2pa library directly, either as an npm package, Rust crate, or bundled SDK, and determine its version from your dependency manifest or compiled binary
    Affected if the Adobe C2pa version is below 0.80.1
  4. Verify input processing paths
    Inspect your codebase for locations where data from untrusted sources is passed to c2pa-web or c2pa-v library functions, particularly image or manifest parsing code
    Affected if the libraries process external or user-supplied content without prior validation

Your environment is affected if you have c2pa-web below 0.7.1, c2pa-v at or below 0.78.2, or Adobe C2pa below 0.80.1 installed and these libraries process external input.

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

Update to a patched version of c2pa-web and c2pa-v libraries once available; until then, implement input validation and bounds checking on data processed by these libraries to prevent crash-inducing inputs.

Recommended fix High confidence

C2pa to version 0.80.1 or later; C2pa Web to version 0.7.1 or later

  1. Identify whether your project uses c2pa or c2pa-web package (or both) by reviewing your dependencies
  2. For JavaScript/Node.js projects: Run 'npm list c2pa' or 'npm list c2pa-web' to check current version
  3. For JavaScript/Node.js projects: Run 'npm update c2pa@latest' or 'npm update c2pa-web@latest' to upgrade to the latest version
  4. For Rust projects: Update the Cargo.toml dependency to c2pa = "0.80.1" or c2pa = "0.7.1" respectively
  5. Verify the upgrade was successful by running 'npm list c2pa' or checking Cargo.lock
  6. Rebuild and test the application to ensure the upgrade does not break existing functionality
Caveat Review the c2pa changelog for any breaking changes between your current version and 0.80.1/0.7.1 before upgrading

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

Fix this in C2pa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34668 — 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-34668 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