C2paApplication · Adobe
CVE-2026-48351
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 is 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 contains an improper input validation vulnerability that allows unauthenticated attackers to send specially crafted input to crash the application, causing a denial-of-service condition 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.84.0<= 0.7.0<= 0.17.0CVSS 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 installed Adobe C2pa productCheck which Adobe C2pa component is installed in your environment. Look for package names like 'c2pa', 'c2pa-web', or 'c2patool' in your package manager, dependencies, or application inventory.Affected if Any of these products are present (Adobe C2pa, Adobe C2pa Web, or Adobe C2patool)
-
Determine the installed version of Adobe C2paRun 'npm list c2pa' for Node.js projects, 'pip show c2pa' for Python, or check the Cargo.toml/dependencies file for Rust projects. For web deployments, check the JavaScript bundle or package.json for c2pa-web version.Affected if Version is 0.84.0 or lower for Adobe C2pa, 0.7.0 or lower for Adobe C2pa Web, or 0.17.0 or lower for Adobe C2patool
-
Compare version against affected rangesDocument the exact version number found and compare it to the affected ranges: Adobe C2pa <= 0.84.0, Adobe C2pa Web <= 0.7.0, Adobe C2patool <= 0.17.0Affected if The installed version falls within or below these version numbers
-
Verify the application processes external inputConfirm that your deployment of the C2pa component accepts or processes any external input, such as image files, manifests, or API requests. Review your application logs for crash events or exceptions related to C2pa processing.Affected if The application processes external input and has experienced unexplained crashes or denial-of-service events
You are affected if you have Adobe C2pa <= 0.84.0, Adobe C2pa Web <= 0.7.0, or Adobe C2patool <= 0.17.0 installed and the application processes external input.
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 dataImplement robust input validation and bounds checking on all user-supplied data to prevent malformed input from triggering application crashes. Consider adding error handling and resource limits to gracefully manage invalid input.
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-48351 — 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-48351 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