{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18036 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-18036 is a high-severity vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18036 and fix it if it is affected.\n\nWhat it is: CVE-2026-18036 is a high-severity vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18036 in the wild and no public exploit code.\n\nAffected product: Legion of the Bouncy Castle Inc. BC-JAVA. 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-2026-18036/ (Markdown: https://insights.sbomify.com/CVE-2026-18036/index.md)","id":"CVE-2026-18036","markdown":"https://insights.sbomify.com/CVE-2026-18036/index.md","name":"CVE-2026-18036","record":{"aliases":["CLEANSTART-2026-AC10204","CLEANSTART-2026-NB89107","CLEANSTART-2026-RL38047","DEBIAN-CVE-2026-18036","GHSA-frjj-v5w4-68pc","UBUNTU-CVE-2026-18036"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java cryptography library","requires_auth":"none","summary":"Timing side-channel in Bouncy Castle NTRU allows attackers to recover private key information via non-constant-time integer divisions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"bcorg","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/U:Amber","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"In Bouncy Castle for Java before 1.86, NTRU reduced secret values with the % operator in three helpers whose reference implementations are deliberately division-free, so each reduction was carried out by an integer division whose latency depends on the secret operand. Polynomial.modQ divided by a variable divisor, which a compiler cannot strength-reduce to a multiply the way it can a constant one, so it emitted a division on every call including on the decapsulation path where the dividend derives from the private key; Polynomial.mod3 and NTRUSampling.mod3 divided the secret key polynomials f and g during key generation, the message polynomials r and m during encapsulation, and coefficients recovered during decapsulation. An attacker able to measure that timing can recover information about the NTRU private key. modQ now masks, which is exact because q is always a power of two, and mod3 uses the reference implementation's division-free fold and select; the results are unchanged.","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":"NTRU leaks private key information by reducing secret values with a non-constant-time integer division","id":"CVE-2026-18036","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Create by Mediavine \u003c 2.5.4 - Unauthenticated Unpublished Content Disclosure and Publication","id":"CVE-2026-18037"},"packages":[],"prev":{"headline":"User Access Manager \u003c 2.3.15 - Unauthenticated Restricted Content Disclosure via REST API","id":"CVE-2026-18035"},"products":["BC-JAVA"],"published":"2026-10-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-02","vendors":["Legion of the Bouncy Castle Inc."]},"summary":"Timing side-channel in Bouncy Castle NTRU allows attackers to recover private key information via non-constant-time integer divisions.","url":"https://insights.sbomify.com/CVE-2026-18036/"}