Skip to main content

CVE-2026-122098Adobe Content Credentials Rust SDK improper certificate validation

Low priorityMedium5.1EPSS not scored yet

CVE-2026-122098 is a improper certificate validation in Adobe Content Credentials Rust SDK, rated medium (5.1 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Awaiting Analysis

What it is

TLS certificates are not checked properly, so an attacker on the path can pose as the server.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place Adobe Content Credentials Rust SDK runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
  • Signature checks. The flaw sits on the network path between clients and services.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.

Questions to answer about your own systems

  • Where does Adobe Content Credentials Rust SDK run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.