dbcve.org
C2paApplication · Adobe

CVE-2026-34678

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 the CAI Content Credentials libraries (c2pa-web and c2pa-v). The vulnerability allows attackers to exhaust system resources without user interaction, leading to denial-of-service. The specific resource consumption mechanism is not detailed, but the affected library versions ([email protected], c2pa-v0.78.2 and earlier) lack proper resource limits or bounds checking during content credential processing.

MitigationUpgrade to patched versions of c2pa-web and c2pa-v libraries beyond the vulnerable releases. Additionally, implement application-level resource limits and monitoring to detect and mitigate resource exhaustion attempts.

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 installed c2pa-web version
    Check package.json, yarn.lock, or npm list for the c2pa-web package version
    Affected if version is 0.7.0 or lower (below 0.7.1)
  2. Identify installed Adobe C2pa (c2pa) version
    Check Cargo.toml, package.json, or dependency lock files for the c2pa or c2pa-v package version
    Affected if version is 0.78.2 or lower (below 0.80.1)
  3. Verify application uses content credential processing
    Search codebase for imports and usage of c2pa-web or c2pa libraries, specifically calls to manifest creation, signing, or verification functions
    Affected if the libraries are imported and used in the application code
  4. Check runtime dependency manifests
    Review any lock files (package-lock.json, yarn.lock, Cargo.lock) to confirm the exact resolved versions of dependencies
    Affected if the resolved version falls within the affected ranges

A user is affected if their application depends on c2pa-web version < 0.7.1 or c2pa/c2pa-v version < 0.80.1 and uses those libraries to process content credentials.

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 patched versions of c2pa-web and c2pa-v libraries beyond the vulnerable releases. Additionally, implement application-level resource limits and monitoring to detect and mitigate resource exhaustion attempts.

Recommended fix High confidence

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

  1. 1. Identify which C2pa library is in use: c2pa (Rust SDK) or c2pa-web (JavaScript SDK)
  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 by updating the dependency in your package manager (e.g., cargo update, npm update, or equivalent)
  4. 4. For c2pa-web users: upgrade to version 0.7.1 or later by updating the JavaScript dependency
  5. 5. Rebuild and redeploy the application
  6. 6. Verify the application functions correctly after the upgrade
Caveat Review release notes for any breaking changes between your current version and the target 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
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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