{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69418 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-69418 is a medium-severity vulnerability in Openssl Openssl, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-69418 and fix it if it is affected.\n\nWhat it is: CVE-2025-69418 is a medium-severity vulnerability in Openssl Openssl, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-69418 in the wild and no public exploit code.\n\nAffected product: Openssl Openssl. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-69418/ (Markdown: https://insights.sbomify.com/CVE-2025-69418/index.md)","id":"CVE-2025-69418","markdown":"https://insights.sbomify.com/CVE-2025-69418/index.md","name":"CVE-2025-69418","record":{"aliases":["ALPINE-CVE-2025-69418","AZL-75272","AZL-75783","AZL-75899","AZL-76128","AZL-76158","AZL-76200","AZL-78546","BELL-CVE-2025-69418","DEBIAN-CVE-2025-69418","ECHO-2c1d-6266-fce5","GHSA-78qr-24v5-7q73","JLSEC-2026-262","MINI-4fp7-99hp-c5m2","MINI-qg2w-mv6w-hjxw","MINI-x6h8-hw8q-62mp","OESA-2026-1613","OESA-2026-1663","ROOT-OS-ALPINE-317-CVE-2025-69418","UBUNTU-CVE-2025-69418"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"OpenSSL cryptographic library","requires_auth":"none","summary":"Direct low-level OCB API calls on hardware-accelerated builds may leave trailing bytes unencrypted and unauthenticated, exposing data to attackers.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openssl","cpe":[{"product":"openssl","vendor":"openssl"}],"cvss":{"score":4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-325","name":"Missing Cryptographic Step"}],"description":"Issue summary: When using the low-level OCB API directly with AES-NI or\u003cbr\u003eother hardware-accelerated code paths, inputs whose length is not a multiple\u003cbr\u003eof 16 bytes can leave the final partial block unencrypted and unauthenticated.\u003cbr\u003e\u003cbr\u003eImpact summary: The trailing 1-15 bytes of a message may be exposed in\u003cbr\u003ecleartext on encryption and are not covered by the authentication tag,\u003cbr\u003eallowing an attacker to read or tamper with those bytes without detection.\u003cbr\u003e\u003cbr\u003eThe low-level OCB encrypt and decrypt routines in the hardware-accelerated\u003cbr\u003estream path process full 16-byte blocks but do not advance the input/output\u003cbr\u003epointers. The subsequent tail-handling code then operates on the original\u003cbr\u003ebase pointers, effectively reprocessing the beginning of the buffer while\u003cbr\u003eleaving the actual trailing bytes unprocessed. The authentication checksum\u003cbr\u003ealso excludes the true tail bytes.\u003cbr\u003e\u003cbr\u003eHowever, typical OpenSSL consumers using EVP are not affected because the\u003cbr\u003ehigher-level EVP and provider OCB implementations split inputs so that full\u003cbr\u003eblocks and trailing partial blocks are processed in separate calls, avoiding\u003cbr\u003ethe problematic code path. Additionally, TLS does not use OCB ciphersuites.\u003cbr\u003eThe vulnerability only affects applications that call the low-level\u003cbr\u003eCRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with\u003cbr\u003enon-block-aligned lengths in a single call on hardware-accelerated builds.\u003cbr\u003eFor these reasons the issue was assessed as Low severity.\u003cbr\u003e\u003cbr\u003eThe FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected\u003cbr\u003eby this issue, as OCB mode is not a FIPS-approved algorithm.\u003cbr\u003e\u003cbr\u003eOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u003cbr\u003e\u003cbr\u003eOpenSSL 1.0.2 is not affected by this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Unauthenticated/unencrypted trailing bytes with low-level OCB function calls","id":"CVE-2025-69418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"openssl:openssl","products":["openssl:openssl"],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion","id":"CVE-2025-69419"},"packages":[],"prev":{"headline":"Missing authorization in plex.tv backend","id":"CVE-2025-69417"},"products":["OpenSSL"],"published":"2026-01-27","related":[{"cvss_score":10,"headline":"Null dereference in n/a","id":"CVE-2009-3245","kev_date_added":null,"published":"2010-03-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-3738","kev_date_added":null,"published":"2006-09-28"},{"cvss_score":9.8,"headline":"Untrusted Sender DN Used as Format String in CMP Response Validation","id":"CVE-2026-63073","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2016-6309","kev_date_added":null,"published":"2016-09-26"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-0799","kev_date_added":null,"published":"2016-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-2842","kev_date_added":null,"published":"2016-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2003-0545","kev_date_added":null,"published":"2003-10-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["OpenSSL"]},"summary":"Direct low-level OCB API calls on hardware-accelerated builds may leave trailing bytes unencrypted and unauthenticated, exposing data to attackers.","url":"https://insights.sbomify.com/CVE-2025-69418/"}