C2paApplication · Adobe
CVE-2026-34679
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) versions 0.7.0 and 0.78.2 and earlier contain an improper input validation flaw that allows an attacker to crash the application via crafted input, causing denial-of-service without any 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 if c2pa-web library is in useSearch project dependencies for c2pa-web in package.json, package-lock.json, or similar dependency manifest filesAffected if c2pa-web version 0.7.0 or earlier is found, or version is less than 0.7.1
-
Identify if c2pa-v library is in useSearch project dependencies for c2pa-v in package.json, requirements.txt, Cargo.toml, or similar dependency manifest filesAffected if c2pa-v version 0.78.2 or earlier is found, or version is less than 0.80.1 (Adobe C2pa)
-
Inspect bundled library filesIf using a bundled or compiled application, search for c2pa-web.js, c2pa.js, or related library files and check any embedded version strings within themAffected if The library file version string indicates an affected version
The environment is affected if c2pa-web version < 0.7.1 or c2pa-v (Adobe C2pa) version < 0.80.1 is installed and the application processes external input through the CAI Content Credentials 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
Upgrade c2pa-web to a version greater than 0.7.0 and c2pa-v to a version greater than 0.78.2 once patched versions are released, and implement input sanitization/validation on all external data paths.
c2pa >= 0.80.1 or c2pa-web >= 0.7.1
- Identify which C2pa library is in use (c2pa or c2pa-web) in your project
- Check the current version of the library by examining your package.json, Cargo.toml, or equivalent dependency file
- For c2pa: update the dependency to version 0.80.1 or higher
- For c2pa-web: update the dependency to version 0.7.1 or higher
- Run your package manager update command (e.g., npm install, cargo update, pip install) to fetch the fixed version
- Rebuild and test your application to verify the upgrade resolves the vulnerability and doesn't introduce regressions
- Consult the Adobe helpx.adobe.com release notes for any additional migration requirements
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-34679 — 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-34679 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