dbcve.org
C2paApplication · Adobe

CVE-2026-34657

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to after 0.80.1 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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.80.1 and earlier are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could result in an arbitrary file system write. An attacker could leverage this vulnerability to write to unauthorized files or directories outside of intended restrictions. Exploitation of this issue requires user interaction in that a victim must extract a maliciously crafted file.

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

Path traversal vulnerability in CAI Content Credentials libraries (c2pa-web and c2pa-v) allows arbitrary file system writes during file extraction. Maliciously crafted archives can escape the intended directory and write files outside the restricted path, enabling unauthorized file system modification.

MitigationUpgrade c2pa-web to a version newer than 0.7.1 and c2pa-v to a version newer than 0.80.1 to obtain the patch that adds proper path validation during extraction 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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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-web or c2pa-v package is installed
    Check your project's dependencies (package.json, package-lock.json, or node_modules) for packages named 'c2pa-web' or 'c2pa-v' (or '@contentcredentials/c2pa-web' and '@contentcredentials/c2pa-v'). For non-JS environments, check for equivalent package manager or bundler dependency files.
    Affected if Either c2pa-web or c2pa-v appears in your dependencies
  2. Check installed version of c2pa-web
    Run 'npm list c2pa-web' or 'npm list @contentcredentials/c2pa-web' to see the installed version. Compare against the affected range: versions 0.7.1 and earlier are vulnerable.
    Affected if Installed version is 0.7.1 or lower, or the package is present without a version pin that would prevent automatic downgrade
  3. Check installed version of c2pa-v
    Run 'npm list c2pa-v' or check your lockfile for the c2pa-v package version. Compare against the affected range: versions 0.80.1 and earlier are vulnerable.
    Affected if Installed version is 0.80.1 or lower, or the package is present without a version pin that would prevent automatic downgrade
  4. Determine if file extraction feature is in use
    Review your codebase for calls to extraction, unzip, extract, or similar functions provided by the c2pa packages. Check if your application processes content credentials archives, especially from external or untrusted sources.
    Affected if Your application uses the c2pa extraction or archive handling functionality to unpack content credentials files

You are affected if you have c2pa-web version 0.7.1 or earlier, or c2pa-v version 0.80.1 or earlier, AND your application uses the file extraction feature to process archives.

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 a release after 0.80.1
Interim mitigation

Upgrade c2pa-web to a version newer than 0.7.1 and c2pa-v to a version newer than 0.80.1 to obtain the patch that adds proper path validation during extraction operations.

Recommended fix Moderate confidence

c2pa >= 0.80.2 and c2pa-web >= 0.7.2 (or latest stable releases)

  1. 1. Identify all instances of c2pa (C2pa) and c2pa-web (C2pa Web) libraries in your project or application
  2. 2. Check current installed versions using your package manager (e.g., npm list c2pa, npm list c2pa-web, or cargo list for Rust implementations)
  3. 3. Upgrade c2pa library to version 0.80.2 or later
  4. 4. Upgrade c2pa-web library to version 0.7.2 or later
  5. 5. Rebuild and redeploy your application
  6. 6. Test that Content Credentials functionality works correctly with the updated libraries
Caveat Review release notes for potential API changes between versions; minor version upgrades typically have backward compatibility but test thoroughly

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

Fix this in C2pa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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