dbcve.org
C2paApplication · Adobe

CVE-2026-34673

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 Uncontrolled Resource Consumption vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to exhaust system resources, resulting in an application 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

This is an Uncontrolled Resource Consumption vulnerability in CAI Content Credentials libraries (c2pa-web and c2pa-v) that could allow an attacker to exhaust system resources through malicious or malformed content credential data, leading to application denial-of-service. The vulnerability requires no user interaction to exploit.

MitigationUpdate c2pa-web to version greater than 0.7.0 and c2pa-v to version greater than 0.78.2 once patches are available, or implement resource consumption limits/quotas around content credential processing operations.

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 library is installed
    Search your project's dependency files (package.json, requirements.txt, Cargo.toml, Gemfile, etc.) for 'c2pa', 'c2pa-v', or 'adobe-c2pa' packages, or run a dependency scan command such as 'npm list c2pa', 'pip show c2pa', or equivalent for your package manager
    Affected if The c2pa or c2pa-v library appears in your dependencies
  2. Check c2pa library version
    Run 'npm list c2pa' for Node.js projects, 'pip show c2pa' for Python, or inspect your lockfile (package-lock.json, Pipfile.lock) to find the exact installed version of the c2pa or c2pa-v library
    Affected if The installed version is lower than 0.80.1 (e.g., 0.78.0, 0.79.0, etc.)
  3. Identify if c2pa-web library is installed
    Search dependency files or run 'npm list c2pa-web' to check if the c2pa-web library is present in your project
    Affected if The c2pa-web library appears in your dependencies
  4. Check c2pa-web library version
    Run 'npm list c2pa-web' or inspect your lockfile to determine the exact installed version of c2pa-web
    Affected if The installed version is lower than 0.7.1 (e.g., 0.6.0, 0.7.0, etc.)
  5. Determine if content credential processing is active
    Review your application code for usage of c2pa libraries to process, validate, or parse content credential data (often found in media handling, image verification, or digital asset management modules)
    Affected if Your application actively uses c2pa or c2pa-web to process content credentials from external sources

You are affected if either c2pa < 0.80.1 or c2pa-web < 0.7.1 is installed AND your application processes content credential data with these libraries.

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 c2pa-web to version greater than 0.7.0 and c2pa-v to version greater than 0.78.2 once patches are available, or implement resource consumption limits/quotas around content credential processing operations.

Recommended fix High confidence

C2pa >= 0.80.1, C2pa Web (c2pa-web) >= 0.7.1

  1. 1. Identify which C2pa library is in use: either the C2pa SDK or C2pa Web (c2pa-web)
  2. 2. Check the currently installed version of the library in your project dependencies
  3. 3. For C2pa users: upgrade to version 0.80.1 or later
  4. 4. For C2pa Web users: upgrade to version 0.7.1 or later
  5. 5. Update the dependency in your package manager (e.g., npm, cargo, or Maven depending on your setup)
  6. 6. Rebuild and redeploy the application
  7. 7. Verify the application functions correctly with the new version

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

Fix this in C2pa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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