C2paApplication · Adobe
CVE-2026-34712
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 · uneditedCAI 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 confidenceCAI Content Credentials library (c2pa) versions [email protected] and c2pa-v0.80.1 and earlier contain improper input validation that allows remote attackers to crash the application via malformed input without any user interaction, causing denial of service.
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
<= 0.80.1<= 0.7.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify c2pa library versionCheck your project dependencies (package.json, Cargo.toml, or similar) for the c2pa or c2pa-web package versionAffected if The version listed is c2pa-web <= 0.7.1 or c2pa <= 0.80.1
-
Determine library usage in applicationSearch your codebase for imports or require statements referencing 'c2pa' or 'c2pa-web' packages, and identify where Content Credentials data is processedAffected if The application imports and uses c2pa or c2pa-web to process Content Credentials data
-
Inspect input handling for Content CredentialsReview code that handles external Content Credentials data (uploaded files, API inputs, URL parameters) and verify whether malformed data is validated before passing to the c2pa libraryAffected if Content Credentials input is passed directly to c2pa without validation, or validation is absent in the code path
-
Verify library is exposed to untrusted inputCheck if the c2pa library processes data from untrusted sources (user uploads, external APIs, network requests) without prior validationAffected if The application processes Content Credentials from untrusted sources directly through the vulnerable library version
You are affected if your application uses c2pa-web <= 0.7.1 or c2pa <= 0.80.1 and processes untrusted Content Credentials data through the library without additional input validation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to versions beyond [email protected] and c2pa-v0.80.1 that include proper input validation fixes; until patches are available, implement input filtering at application boundaries to reject malformed content credentials data.
Upgrade to c2pa > 0.80.1 and c2pa-web > 0.7.1 (latest stable release recommended)
- Identify the specific C2pa library or package in use (c2pa for Rust or c2pa-web for JavaScript)
- Check current installed version using package manager (e.g., cargo list for Rust, npm list for JavaScript)
- Upgrade to the latest available version beyond 0.80.1 for c2pa or beyond 0.7.1 for c2pa-web
- Verify the upgrade by running tests and confirming the application functions correctly
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
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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