dbcve.org
C2paApplication · Adobe

CVE-2026-47903

MEDIUM · 6.2 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to after 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.80.1 and earlier are affected by an Improper Input Validation vulnerability. 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 libraries (c2pa-web and c2pa-v) versions 0.7.1 and 0.80.1 and earlier contain an improper input validation vulnerability. Attackers can exploit this by providing specially crafted input to crash the application, causing a denial-of-service condition without requiring any user interaction.

MitigationUpdate to a patched version of the c2pa-web and c2pa-v libraries once released, and implement robust input validation on all data processed by these libraries to prevent malformed input from reaching vulnerable parsing code.

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-web library usage
    Search your codebase, dependencies, or installed packages for 'c2pa-web' package. Check package.json, requirements.txt, or similar dependency files, or run 'npm list c2pa-web' or 'pip list | grep c2pa'
    Affected if The c2pa-web package is present in your dependencies
  2. Check c2pa-web version
    Run 'npm list c2pa-web' or check your package-lock.json/package.json for the installed version of c2pa-web
    Affected if The installed version is 0.7.1 or earlier (any version <= 0.7.1)
  3. Identify c2pa-v library usage
    Search your codebase, dependencies, or installed packages for 'c2pa-v' or 'c2pa' package. Check package.json, requirements.txt, or similar dependency files, or run 'npm list c2pa-v' or 'pip list | grep c2pa'
    Affected if The c2pa-v or c2pa package is present in your dependencies
  4. Check c2pa-v version
    Run 'npm list c2pa-v' or check your package-lock.json/package.json for the installed version of c2pa-v (sometimes listed as 'c2pa')
    Affected if The installed version is 0.80.1 or earlier (any version <= 0.80.1)
  5. Verify content credentials processing is in use
    Inspect your application code for imports or usage of c2pa-web or c2pa-v modules for processing content credentials, manifests, or asset signatures
    Affected if Your application uses these libraries to process content credentials from external sources

You are affected if your project uses c2pa-web version 0.7.1 or earlier, or c2pa-v version 0.80.1 or earlier, and processes content credentials from external 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 a release after 0.80.1
Interim mitigation

Update to a patched version of the c2pa-web and c2pa-v libraries once released, and implement robust input validation on all data processed by these libraries to prevent malformed input from reaching vulnerable parsing code.

Recommended fix Moderate confidence

c2pa version 0.80.2 or later; c2pa-web version 0.7.2 or later

  1. Locate the dependency management file for your project (e.g., package.json, Cargo.toml, pom.xml, or requirements.txt)
  2. Update the c2pa dependency version to 0.80.2 or later
  3. Update the c2pa-web dependency version to 0.7.2 or later
  4. Run your project's dependency update command (npm update, cargo update, etc.)
  5. Rebuild and test your application to verify the fix is applied

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

Fix this in C2pa Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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