AI Science Tracker

OCB low-level API leaves trailing bytes unauthenticated

OpenSSL · AI involvement attributed to AISLE autonomous analyzer (specific model/version not disclosed)

Finding and attribution

On hardware-accelerated builds, direct low-level OCB encrypt/decrypt calls with a non-block-aligned input may leave the trailing 1–15 bytes exposed or unauthenticated. OpenSSL says typical EVP consumers are unaffected and TLS does not use OCB suites.

Product: OpenSSL. AI system: AISLE autonomous analyzer (specific model/version not disclosed). Team / organization: AISLE.

CVE identifiers: CVE-2025-69418.

AI and human contribution (source account): AISLE’s January 26, 2026 article says its autonomous analyzer found all 12 CVEs in OpenSSL’s January coordinated release, and individually names this case. OpenSSL’s own vulnerability record credits the named Aisle Research finder(s) for CVE-2025-69418; OpenSSL’s January 27 security advisory gives the flaw and report chronology. The exact model and division of AI versus researcher analysis are not public. OpenSSL credits Stanislav Fort (Aisle Research) as finder and fix developer. AISLE says its autonomous analyzer found all 12 cases; exact human/AI division is not stated.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: OpenSSL published the vendor advisory and released fixes on January 27, 2026. The AISLE public AI attribution article appeared January 26, one day before the public vendor disclosure. No claim of in-the-wild exploitation is made.

Remediation status: fix documented. OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19 and 1.1.1ze (premium-support branch). See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 27 Jan 2026. AI attribution dated 26 Jan 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 4. Documented technical effects: data disclosure, data modification.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

CVE-2025-69418: data disclosure, data modification.
Prerequisites / affected scope: Only direct low-level CRYPTO_ocb128_encrypt/decrypt calls with non-block-aligned inputs on hardware-accelerated builds: trailing 1–15 bytes can be cleartext and omitted from authentication, so they can be read or tampered with undetected. EVP callers are not affected..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19 and 1.1.1ze (premium-support branch). See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases