dbcve.org
C2paApplication · Adobe

CVE-2026-48298

MEDIUM · 6.2 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to after 0.84.0 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click 5 weeks old

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 · unedited
CAI Content Credentials is affected by an Integer Underflow (Wrap or Wraparound) 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 confidence

CAI Content Credentials contains an integer underflow vulnerability where arithmetic operations can produce values below the minimum representable integer, causing wraparound. This can trigger memory corruption or invalid memory access that crashes the application, resulting in denial of service.

MitigationApply any available vendor patch for CAI Content Credentials. If no patch exists, implement proper bounds checking and validation on integer arithmetic operations to prevent underflow conditions.

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
Affected:<= 0.84.0
C2pa WebApplication
Affected:<= 0.7.0
C2patoolApplication
Affected:<= 0.17.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Adobe C2Pa is installed
    Run 'pip show c2pa' or check for c2pa library in your Python environment, or check the application's dependencies for 'c2pa' package
    Affected if The installed version is 0.84.0 or lower
  2. Identify if Adobe C2Pa Web is installed
    Run 'pip show c2pa-web' or check for c2pa-web package in your dependencies
    Affected if The installed version is 0.7.0 or lower
  3. Identify if C2Patool is installed
    Run 'c2patool --version' or check for c2patool in your PATH and installed binaries
    Affected if The installed version is 0.17.0 or lower
  4. Verify Content Credentials processing is in use
    Check if your application or workflow processes CAI (Content Authenticity Initiative) Content Credentials, manifests, or signed metadata using the C2Pa library
    Affected if The application processes Content Credentials and uses an affected C2Pa library version

A user is affected if any of Adobe C2Pa (<=0.84.0), Adobe C2Pa Web (<=0.7.0), or C2Patool (<=0.17.0) is installed and processes Content Credentials, as the integer underflow will trigger during arithmetic operations in the affected code paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 0.84.0
Interim mitigation

Apply any available vendor patch for CAI Content Credentials. If no patch exists, implement proper bounds checking and validation on integer arithmetic operations to prevent underflow conditions.

Recommended fix Moderate confidence

C2pa >= 0.85.0 | C2pa Web >= 0.8.0 | C2patool >= 0.18.0

  1. 1. Identify which C2pa component(s) are in use: C2pa SDK, C2pa Web, or C2patool
  2. 2. For C2pa SDK: Update the c2pa crate dependency in your project to version 0.85.0 or later
  3. 3. For C2pa Web: Update the @contentcredentials/verify package to version 0.8.0 or later
  4. 4. For C2patool: Update the c2patool package to version 0.18.0 or later
  5. 5. Rebuild and test the application to ensure the integer underflow vulnerability is remediated
  6. 6. Verify the fix by confirming the application no longer crashes when processing crafted Content Credentials
Caveat Minor version upgrades unlikely to introduce breaking changes; however, review release notes for any API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in C2pa Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48298 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48298 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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