EUVD-2026-100718
GHSA-x6r6-vg44-phx6
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft content with forged/invalid signature
-
ExploitSubmit to SDK verification path
-
ExecutionBypass improper cryptographic signature check
-
ImpactGain unauthorized write access and tamper with content credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | The target application must use the CAI Content Credentials SDK's signature-verification/validation path and trust its verdict to establish content authenticity or authorization; the attacker supplies content bearing a forged or improperly-signed credential that the flawed verification accepts, requiring no authentication (PR:N) and no user interaction (UI:N). Limiting factors: impact is confined to integrity of content provenance and the 'write access' the SDK's trust decision gates - there is no confidentiality or availability impact (C:N/A:N) - so real-world risk is highest in deployments that make security or publishing decisions based solely on SDK-verified Content Credentials, and negligible where the SDK's result is not a trust boundary. Exact vulnerable/fixed versions are not provided in the input and must be confirmed against APSB26-163. |
| Impact | CVSS base score is 7.5 (High) driven entirely by a single integrity impact (I:H) with no confidentiality or availability loss, reflecting that this is a signature-verification bypass (CWE-347) rather than a code-execution or data-disclosure flaw. The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes an attractive profile - remote, low-complexity, no privileges, no user interaction - which the description corroborates ('does not require user interaction'). However, NO exploitation-probability signals accompany the input: EPSS is absent, the CVE is NOT in CISA KEV, and no POC is referenced, so there is no public exploit identified at time of analysis. The practical impact is narrower than the 7.5 suggests: the attacker gains 'unauthorized write access' by forging or bypassing Content Credentials cryptographic signatures, undermining content provenance/authenticity integrity rather than compromising the host system. No SSVC decision data (exploitation status, automatable, technical impact) was provided to cross-reference. Net assessment: a credible integrity-focused issue that matters acutely for workflows that trust Content Credentials signatures, but with no evidence of active or widespread exploitation it is a prioritize-if-exposed issue rather than an emergency patch-now item. |
| Exploit ScenarioDerived | An attacker crafts a media asset or token whose cryptographic signature is malformed or forged, then submits it to an application that relies on the CAI Content Credentials SDK to validate provenance. Because the SDK improperly verifies the signature, the forged content is accepted as authentic, letting the attacker tamper with or inject content credentials and obtain unauthorized write access. No POC is referenced in the provided data, and exploitation requires no user interaction (UI:N). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Improper verification of cryptographic signatures in the CAI Content Credentials SDK allows unauthenticated remote attackers to supply forged or improperly signed content credentials that the SDK accepts as authentic, bypassing the security check and gaining unauthorized write access to whatever the SDK's verification verdict gates. The CVSS 3.1 base score is 7.5 (High) under the vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N - an integrity-only signature-verification bypass (CWE-347) with no confidentiality or availability impact, requiring no authentication and no user interaction. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; real-world risk is highest in deployments that make publishing, authorization, or authenticity decisions solely on the SDK's verification result, and negligible where that result is not treated as a trust boundary.
RemediationAI
Primary remediation is to update the CAI Content Credentials SDK to the fixed release specified in Adobe security bulletin APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html); the exact fixed version is not stated in the provided data, so the bulletin must be consulted to confirm the version string before deploying. Vendor-released patch availability should be treated as 'per advisory' until that version is confirmed. Where immediate upgrade is not possible, apply compensating controls tailored to the bypass: stop treating the SDK's verification verdict as the sole trust boundary - re-verify credentials server-side with an independent implementation and, for high-value actions, require a second out-of-band authorization check (trade-off: added latency and engineering effort, but it removes the single point of failure); enforce a strict allowlist of expected signing algorithms and explicitly reject unsigned, 'none', or unexpected-algorithm credentials, and pin the trusted issuers, key IDs, and certificate chains rather than trusting signer-supplied header values (trade-off: legitimate credential issuers outside the allowlist will be rejected and must be onboarded deliberately); restrict the write endpoints and publishing actions gated by SDK verification to authenticated, authorized principals so that a forged credential alone cannot trigger a state change (trade-off: changes existing workflows that assumed credential-only authorization); and instrument verifier logging for rejected-but-then-accepted credentials and anomalous signer headers to detect probing. Because exploitation requires no authentication or user interaction, exposed verification services should also be rate-limited and monitored, and any content already accepted via the flawed verifier should be re-validated after patching, since prior 'authorized' writes may have been forged.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Content Credentials (the Content Authenticity Initiative's provenance standard, aligned with C2PA) work by attaching cryptographically signed assertions and manifests to media, so that a verifier can establish who created or modified the content. The security of that model rests entirely on correct verification of the cryptographic signature and its certificate/attestation chain. CVE-2026-95632 is an instance of CWE-347, Improper Verification of Cryptographic Signature - meaning the SDK's verification path fails to properly validate the signature (for example by not enforcing the signing algorithm, accepting an unexpected or absent algorithm, failing to bind the signature to the claimed signer/key, or failing to validate the certificate chain of trust) and returns a positive authenticity verdict for attacker-supplied input. The accompanying intelligence tags (Authentication Bypass, Jwt Attack) indicate the credential is token-like and that the flaw follows the well-known JWT failure classes - algorithm confusion/algorithm substitution, 'none'/'unsigned' acceptance, signature stripping, or key/certificate confusion - where the verifier trusts attacker-controlled header or key material instead of pinning it. Per the assessed vector the attack is network-delivered, requires no privileges (PR:N) and no user interaction (UI:N), and is uniform in scope (S:U); the sole impact is integrity (I:H), specifically the unauthorized write access that flows from the SDK's falsified trust decision. Note the assessment explicitly limits impact to the integrity of provenance data and to actions gated by that trust decision; it is not a code-execution or data-disclosure issue, and the exploited component is the verification/validation path, not the signing path.
Know when Jwt Attack gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Signature-bypass is reachable remotely with no auth or interaction (AV:N/AC:L/PR:N/UI:N); only integrity is affected via forged credentials/unauthorized write (I:H), with no confidentiality or availability loss.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
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. Exploitation of this issue does not require user interaction.
Executive ViewAI
The CAI Content Credentials SDK contains a signature-verification bypass that can cause forged content credentials to be treated as authentic, potentially granting unauthorized write access in workflows that rely on the SDK's verdict. Because no vendor-released patch is currently available, organizations that use this SDK as a trust boundary for publishing, authorization, or authenticity decisions face a high integrity risk that could undermine content provenance controls and trigger reputational or compliance consequences. Leadership should prioritize identifying affected deployments and reducing reliance on the SDK's verification result until a fix is available.
No vendor-released patch identified at time of analysis. Interim mitigations include independent cryptographic verification outside the SDK, treating SDK verdicts as untrusted, restricting write access gated by verification results, enforcing least privilege, and monitoring for forged credentials and vendor updates.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
Exploit-DB