cve.bz

CVE-2026-65625 potatosalad jose

5.9 mediumEPSS 0.1%Fix available

Medium (5.9) in potatosalad jose. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in jose 1.11.13.

On this page
The pure-Erlang AES-GCM fallback in jose_jwa_aes derives the number of verified authentication tag bits from the attacker-supplied tag itself. In the {aes_gcm, Bits} clause of block_decrypt/4, the incoming tag is guarded only by is_binary/1, with no check on its length. Verification in gcm_block_decrypt/6 then computes TBits = bit_size(T) and compares only those bits of the real 128-bit tag. An attacker who controls a JWE token can truncate the authentication tag to as little as 8 bits, so only 8 bits are ever checked. This reduces forgery resistance from 2^-128 to 2^-8, and a forged ciphertext is reliably accepted as authentic within 256 attempts without knowledge of the key (an authentication tag forgery and integrity bypass). Supplying a tag longer than 128 bits instead causes a badmatch that crashes the decrypting process. The fallback is reached through the public JWE decryption path whenever AES-GCM is not provided by a native crypto NIF, for example on FIPS or stripped or older OTP builds. This issue affects jose: from 1.2.0 before 1.11.13.

Severity

CVSS 4.0

5.9 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-354 Improper Validation of Integrity Check Value
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-65625 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-65625?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-65625?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-65625 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
potatosalad josefrom 1.2.0 before 1.11.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-65625Hexjose>=1.2.0 <1.11.131.11.13
EEF-CVE-2026-65625no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13erlang-joseno fix listedDEBIAN-CVE-2026-65625
Debian14erlang-jose1.11.13-1DEBIAN-CVE-2026-65625
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 morejoseno fix listedUBUNTU-CVE-2026-65625
Azure Linux3rabbitmq-serverno fix listedAZL-112187

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because successful integrity bypass and denial-of-service conditions require an uncommon deployment environment where native cryptographic acceleration is absent. In standard Red Hat environments, Erlang runtimes are built with native OpenSSL-backed crypto NIF support, which handles AES-GCM operations and avoids the affected pure-Erlang fallback routine. Consequently, systems operating under standard enterprise configurations are not exposed to this flaw, restricting the risk to specialized setups lacking native cryptographic libraries.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-65625.

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON