dbcve.org
C2paApplication · Adobe

CVE-2026-34669

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 Improper Input Validation 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 0.7.0 and earlier and 0.78.2 and earlier respectively contain an improper input validation flaw. An attacker can provide malicious input to the library that triggers a crash in the consuming application, resulting in denial-of-service without requiring any user interaction.

MitigationUpdate c2pa-web to version 0.7.1 or later and c2pa-v to version 0.78.3 or later to obtain the patched library that properly validates input before processing.

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 library usage
    Search project dependencies, package.json, Cargo.toml, or node_modules for c2pa-web or c2pa-v packages. Also check for npm list, pip list, or other package manager listings that may reference these components.
    Affected if The c2pa-web or c2pa-v packages are present in the environment
  2. Check c2pa-web version
    Run npm list c2pa-web or yarn list c2pa-web to retrieve the installed version. If using a different package manager, use the appropriate command to query the c2pa-web package version.
    Affected if The installed version is 0.7.0 or earlier, which is less than 0.7.1
  3. Check c2pa-v version
    Run npm list c2pa-v or yarn list c2pa-v to retrieve the installed version. Check Cargo.lock or other dependency files if using Rust. Use the relevant package manager command to query the c2pa-v package version.
    Affected if The installed version is 0.78.2 or earlier, which is less than 0.78.3
  4. Verify Adobe C2pa SDK version
    If using the Adobe C2pa SDK directly rather than the web components, check the package version for the Adobe C2pa library in use. Query via the appropriate package manager or inspect lock files.
    Affected if The installed version is less than 0.80.1
  5. Confirm input processing context
    Review application code to determine if the c2pa library processes input from untrusted sources such as user-uploaded files, API payloads, or external data streams. Check for code that calls c2pa parsing or validation functions on external content.
    Affected if The application processes untrusted input through the vulnerable c2pa components

A user is affected if their environment contains c2pa-web version 0.7.0 or earlier, c2pa-v version 0.78.2 or earlier, or Adobe C2pa SDK version below 0.80.1, and that library processes input from untrusted sources.

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 0.7.1 or later and c2pa-v to version 0.78.3 or later to obtain the patched library that properly validates input before processing.

Recommended fix High confidence

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

  1. Identify which C2pa library is in use: C2pa (the core SDK) or C2pa Web (the web/JS library
  2. If using C2pa core SDK, upgrade to version 0.80.1 or later
  3. If using C2pa Web (c2pa-web), upgrade to version 0.7.1 or later
  4. For JavaScript/Node.js projects, update the dependency in package.json: run 'npm install c2pa-web@^0.7.1' or 'npm update c2pa-web'
  5. For other package managers, use the equivalent update command for your ecosystem
  6. After upgrading, rebuild the application and verify that the Content Credentials functionality still works as expected
  7. Test that previously created or signed content credentials can still be validated

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
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,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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