C2paApplication · Adobe
CVE-2026-34713
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 Uncontrolled Resource Consumption vulnerability. An attacker could exploit this vulnerability to exhaust system resources, resulting in an application 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 · high confidenceCAI Content Credentials libraries (c2pa-web and c2pa-v) versions 0.7.1/0.80.1 and earlier contain an uncontrolled resource consumption vulnerability during content credential parsing/processing. An attacker can supply malicious or excessively large credential data that causes unbounded resource allocation (likely memory or CPU), leading to denial of service without any user interaction required.
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.
-
Locate c2pa-web library in your projectSearch your codebase for c2pa-web: check package.json, package-lock.json, or yarn.lock for 'c2pa-web' as a dependencyAffected if c2pa-web is present with version <= 0.7.1
-
Locate c2pa-v library in your projectSearch your codebase for c2pa-v or adobe-c2pa: check package.json, package-lock.json, or yarn.lock for 'c2pa-v' or 'adobe-c2pa' as a dependencyAffected if c2pa-v/adobe-c2pa is present with version <= 0.80.1
-
Verify installed library versionsRun 'npm list c2pa-web c2pa-v' or 'yarn list c2pa-web c2pa-v' to list installed versions, or inspect node_modules/c2pa-web/package.json and node_modules/c2pa-v/package.jsonAffected if Either library version falls within or below the affected ranges (c2pa-web <= 0.7.1, c2pa-v <= 0.80.1)
-
Confirm usage of Content Credentials processingSearch your codebase for imports and usage of c2pa-web or c2pa-v modules, such as 'require c2pa-web' or 'import { ... } from c2pa-v'Affected if Your application imports and uses either library to process Content Credentials
You are affected if your project depends on c2pa-web <= 0.7.1 or c2pa-v <= 0.80.1 and uses these libraries to process Content Credentials from untrusted sources.
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.
From vendor dataUpdate c2pa-web to version 0.7.2 or later and c2pa-v to version 0.80.2 or later to obtain the vendor patch that adds resource consumption limits. If patching is not immediately possible, implement upstream rate limiting or input validation on credential data ingestion.
Fix this in C2pa
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34713 — 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-34713 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