dbcve.org
C2paApplication · Adobe

CVE-2026-34667

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 Integer Underflow (Wrap 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 confidence

A content credentials library (c2pa) contains an integer underflow vulnerability in versions [email protected] and c2pa-v0.78.2 and earlier. The vulnerability can be triggered without user interaction, causing the application to crash and resulting in a denial-of-service condition.

MitigationUpdate to patched versions of the c2pa-web and c2pa libraries once released; implement proper bounds checking on integer operations in the affected code paths to prevent wraparound.

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 package usage
    Search for c2pa-web in package.json, package-lock.json, or yarn.lock files within your project or installed node_modules
    Affected if c2pa-web version is present and below 0.7.1
  2. Check c2pa-web installed version
    Run 'npm list c2pa-web' or 'yarn list c2pa-web' to see the installed version, or inspect node_modules/c2pa-web/package.json for the version field
    Affected if The installed version is 0.7.0 or earlier
  3. Identify c2pa Rust crate usage
    Search Cargo.toml files for c2pa dependency, or run 'cargo tree -p c2pa' to see if the crate is included in your project
    Affected if c2pa crate is listed as a dependency in Cargo.toml
  4. Check c2pa crate version
    Inspect Cargo.lock for the c2pa crate version, or run 'cargo tree -i c2pa' to see the resolved version
    Affected if The resolved version is 0.78.2 or earlier, or the version specifier in Cargo.toml allows versions below 0.80.1
  5. Verify library is actually loaded at runtime
    Confirm the application actually loads and uses the c2pa or c2pa-web library at runtime - check import statements in source code (e.g., 'use c2pa', 'require c2pa-web')
    Affected if The vulnerable library version is imported and executed in your application code

You are affected if your project depends on c2pa-web version 0.7.0 or earlier, or c2pa crate version 0.78.2 or earlier, and the library code is actually loaded at runtime.

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 patched versions of the c2pa-web and c2pa libraries once released; implement proper bounds checking on integer operations in the affected code paths to prevent wraparound.

Recommended fix High confidence

c2pa >= 0.80.1 OR c2pa-web >= 0.7.1

  1. 1. Identify which C2pa library you are using (c2pa for SDK or c2pa-web for web component)
  2. 2. For c2pa (SDK) users: Update your dependency to version 0.80.1 or later
  3. 3. For c2pa-web users: Update your dependency to version 0.7.1 or later
  4. 4. If using both libraries, update both to their respective fixed versions
  5. 5. Rebuild and redeploy your application
  6. 6. Verify the application starts and runs without crashes

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

Fix this in C2pa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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