# CVE-2026-123261: CAI Content Credentials | Improper Verification of Cryptographic Signature (CWE-347)


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-mcm7-3wgv-7h4c

## What is CVE-2026-123261?

CVE-2026-123261 is a medium-severity vulnerability in Adobe C2PA Tool, published on 10 Nov 2026. 

### Official description

CAI Content Credentials is affected by an Improper Verification of Cryptographic Signature vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-123261?


## How do I fix CVE-2026-123261?

No fix has been published for CVE-2026-123261 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123261 being exploited?

There is no known exploitation of CVE-2026-123261 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123261 and fix it if it is affected.

What it is: CVE-2026-123261 is a medium-severity vulnerability in Adobe C2PA Tool, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123261 in the wild and no public exploit code.

Affected product: Adobe C2PA Tool. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123261/ (Markdown: https://insights.sbomify.com/CVE-2026-123261/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123261
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123261
- OSV: https://osv.dev/vulnerability/CVE-2026-123261

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123261/
Summaries are generated and may contain mistakes; the official description above is the record.