dbcve.org
C2paApplication · Adobe

CVE-2026-34672

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

The CAI Content Credentials library (c2pa-web and c2pa-v components) versions [email protected], c2pa-v0.78.2 and earlier contain an integer underflow vulnerability. An attacker can trigger this condition without user interaction, causing the application to crash and resulting in denial of service.

MitigationUpgrade the c2pa-web and c2pa-v libraries to versions beyond 0.7.0 and 0.78.2 respectively, once patched versions are released by the vendor.

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 if c2pa libraries are in use
    Search project dependencies (package.json, Cargo.toml, requirements.txt, or similar) for 'c2pa-web', 'c2pa-v', or 'c2pa' packages. Also scan node_modules, vendor folders, or deployed binaries for these library names.
    Affected if Any c2pa-web or c2pa-v package is found in dependencies or deployed assets
  2. Check c2pa-web version
    Run 'npm list c2pa-web' for Node.js projects, or inspect the package.json lock file. For other languages, use the appropriate package manager to query the installed version of c2pa-web.
    Affected if The installed version is 0.7.0 or earlier, or any version below 0.7.1
  3. Check c2pa-v version
    Run 'npm list c2pa-v' for Node.js projects, or inspect the package.json lock file. For other languages, use the appropriate package manager to query the installed version of c2pa-v.
    Affected if The installed version is 0.78.2 or earlier, or any version below 0.80.1 for Adobe C2pa
  4. Verify runtime usage of affected components
    If libraries are present but not actively used at runtime, the vulnerability may not be exploitable. Review application code to confirm whether c2pa-web or c2pa-v functions are actually invoked during execution.
    Affected if The libraries are both present AND actively loaded or called by the application

You are affected if your application includes c2pa-web version 0.7.0/earlier or c2pa-v version 0.78.2/earlier (or Adobe C2pa below 0.80.1) and these components are loaded or executed 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

Upgrade the c2pa-web and c2pa-v libraries to versions beyond 0.7.0 and 0.78.2 respectively, once patched versions are released by the vendor.

Recommended fix Moderate confidence

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

  1. 1. Identify all projects or applications that use the C2pa (c2pa) library and verify the current version in use
  2. 2. If using C2pa library, upgrade to version 0.80.1 or later
  3. 3. If using C2pa Web (c2pa-web) library, upgrade to version 0.7.1 or later
  4. 4. For projects using both libraries, apply the corresponding upgrade for each
  5. 5. Rebuild and redeploy the affected applications
  6. 6. Test the application to confirm it functions correctly after the upgrade
Caveat Review the release notes for 0.80.1 and 0.7.1 to check for any breaking changes or API modifications that may require code adjustments

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

Fix this in C2pa Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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