CVE.org (no NVD analysis yet)· CNA adobe

CVE-2026-103294: CAI Content Credentials | Improper Certificate Validation (CWE-295)

Noroxi assessment

Priority: Monitor (action score 23/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

CAI Content Credentials is affected by an Improper Certificate Validation 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.

MediumCVSS 5.9 · v3.1—No exploit No fix recorded

EUVD-2026-100741

Published: Oct 13, 2026
Updated: Oct 17, 2026
EPSS: 0.1% · 9th percentile
CWE: CWE-295

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 23 / 40 · 5.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · adobe: 5.9; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
adobe	c2pa	cpe:2.3:a:adobe:c2pa
adobe	c2pa-web	cpe:2.3:a:adobe:c2pa-web
adobe	c2patool	cpe:2.3:a:adobe:c2patool

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

adobe c2pabefore 0.91.1
adobe c2pa-webbefore 0.15.3
adobe c2patoolbefore 0.28.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

Adobe C2PA Tool
- v0.28.1not affected
- up to and including c2patool-v0.27.15affected
Adobe Content Credentials JS SDK
- @contentauth/c2pa-web@0.15.3not affected
- up to and including @contentauth/c2pa-web@0.13.4affected
Adobe Content Credentials Rust SDK
- c2pa-v0.91.1not affected
- up to and including c2pa-v0.90.15affected

Same product

adobe: all records

Other highest-scoring records for the same primary product.

CVE-2026-95634CAI Content Credentials | Server-Side Request Forgery (SSRF) (CWE-918)
34Monitor
CVE-2026-48290CAI Content Credentials | Server-Side Request Forgery (SSRF) (CWE-918)
32Monitor
CVE-2026-95633CAI Content Credentials | Improper Verification of Cryptographic Signature (CWE-347)
30Monitor

Published before and after this one in the same product

← EarlierCVE-2026-102501Oct 13, 2026 · CAI Content Credentials | Improper Input Validation (CWE-20)
21Monitor
← EarlierCVE-2026-102502Oct 13, 2026 · CAI Content Credentials | Improper Verification of Cryptographic Signature (CWE-347)
21Monitor
Later →CVE-2026-103296Oct 13, 2026 · CAI Content Credentials | Improper Verification of Cryptographic Signature (CWE-347)
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-1001180 days apartCAI Content Credentials | Improper Certificate Validation (CWE-295)
30Monitor
CVE-2026-1001210 days apartCAI Content Credentials | Improper Certificate Validation (CWE-295)
30Monitor
CVE-2026-1001220 days apartCAI Content Credentials | Improper Certificate Validation (CWE-295)
30Monitor
CVE-2026-1001230 days apartCAI Content Credentials | Improper Certificate Validation (CWE-295)
30Monitor
CVE-2026-1001160 days apartCAI Content Credentials | Improper Certificate Validation (CWE-295)
23Monitor
CVE-2026-4843763 days apartCAI Content Credentials | Improper Certificate Validation (CWE-295)
22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd-secondary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
2  // Left empty for the test environment
3}

Fixed

kotlin

1val client = OkHttpClient.Builder()
2  .certificatePinner(
3    CertificatePinner.Builder()
4      .add("api.sirius.example", "sha256/…")
5      .build()
6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

SSVC exploitation— → noneOct 17, 2026, 2:07 AM UTC
Exploit maturity— → noneOct 13, 2026, 11:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records