dbcve.org
C2paApplication · Adobe

CVE-2026-34665

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable 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 · high confidence

CAI Content Credentials (c2pa-web and c2pa-v libraries) versions before 0.7.1 and 0.78.3 contain an uncontrolled resource consumption vulnerability that allows attackers to exhaust system resources through malformed or specially crafted content credential operations, leading to denial-of-service without requiring any user interaction.

MitigationUpgrade to [email protected] or c2pa-v0.78.3 or later. Additionally, implement application-layer resource limits and timeouts around credential processing operations to mitigate exploitation while patches are applied.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 Adobe C2pa libraries are in use
    Search your project dependencies (package.json, Cargo.toml, pom.xml, requirements.txt, or similar) for 'c2pa', 'c2pa-web', 'c2pa-v', or Adobe Content Credentials packages
    Affected if Any c2pa library is present in dependencies
  2. Determine installed c2pa-web version
    Run npm list c2pa-web or check your lockfile for the installed version of c2pa-web package
    Affected if c2pa-web version is present and is less than 0.7.1
  3. Determine installed Adobe C2pa version
    Check your dependency manifest or lockfile for the Adobe C2pa library version (may appear as c2pa, c2pa-v, or @contentauthenticity/c2pa)
    Affected if Adobe C2pa version is present and is less than 0.80.1
  4. Check if application processes content credentials automatically
    Review your application code to determine if it automatically loads, validates, or processes content credential data without explicit user action (this includes automatic parsing of uploaded files, API-driven credential verification, or background credential operations)
    Affected if The application automatically processes content credentials from untrusted sources

You are affected if your environment has Adobe C2pa version below 0.80.1 or c2pa-web version below 0.7.1 and your application processes content credentials automatically.

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 [email protected] or c2pa-v0.78.3 or later. Additionally, implement application-layer resource limits and timeouts around credential processing operations to mitigate exploitation while patches are applied.

Recommended fix High confidence

C2pa: >= 0.80.1 | C2pa Web: >= 0.7.1

  1. Identify which C2pa library is in use in the project (either c2pa or c2pa-web)
  2. For projects using the C2pa library: run the package manager update command to upgrade to version 0.80.1 or later
  3. For projects using the C2pa Web library: run the package manager update command to upgrade to version 0.7.1 or later
  4. Verify the upgrade was successful by checking the installed package version
  5. Test the application to ensure functionality remains intact after the upgrade

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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