C2paApplication · Adobe
CVE-2026-34666
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.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 confidenceCAI Content Credentials libraries (c2pa-web and c2pa-v) contain an improper input validation vulnerability that allows unauthenticated attackers to cause application crashes leading to denial-of-service, without requiring user interaction.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed c2pa library versionCheck your project dependencies (package.json, Cargo.toml, or similar) for c2pa-web or c2pa-v entries and note the version numberAffected if The installed version is below 0.80.1 for c2pa-v or below 0.7.1 for c2pa-web
-
Verify c2pa library is in use at runtimeSearch your codebase for imports or require statements referencing 'c2pa-web', 'c2pa-v', or '@contentcredentials/c2pa'Affected if These libraries are imported and the code path executes credential parsing logic
-
Confirm content credential parsing is enabledReview your application configuration to determine if the Content Credentials parsing feature is active - this is typically controlled by flags such as 'enableC2PA' or similar options in the library initializationAffected if Content credential parsing is enabled and the vulnerable code path can be reached with external input
-
Check for user-controlled credential inputIdentify if your application accepts content credentials from untrusted sources (such as image uploads, API inputs, or external URLs) that feed into the c2pa parsing functionsAffected if Untrusted input reaches the c2pa library without prior validation
-
Review application logs for crashesExamine your application logs for crashes, stack traces, or errors originating from c2pa library code that may indicate exploitation attemptsAffected if Repeated crashes occur in c2pa parsing routines
Your environment is affected if you are running c2pa-v versions below 0.80.1 or c2pa-web versions below 0.7.1, and your application processes untrusted content credentials through the library.
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 · scoped0.7.10.80.1
Update c2pa-web to version >0.7.0 and c2pa-v to version >0.78.2. If patches are unavailable, implement input validation/sanitization around content credential parsing logic.
C2pa version 0.80.1 or later; C2pa Web version 0.7.1 or later
- 1. Identify the specific C2pa library in use (either c2pa or c2pa-web)
- 2. Check the current installed version using your package manager (npm, cargo, or maven depending on the language binding)
- 3. For c2pa-web, upgrade to version 0.7.1 or later
- 4. For c2pa (the Rust SDK), upgrade to version 0.80.1 or later
- 5. Verify the upgrade was successful by checking the installed package version
- 6. Test that the application starts and runs without crashes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in C2pa
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34666 — 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-34666 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