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.
CVE-2026-18036
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 8.2
- EG Score
- 8.2HIGHmedium confidence
- EG Risk
- 37EG Risk 37/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 18th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 2, 2026
Last Modified
October 2, 2026
Advisory Details (2)
Auto-updated Oct 2, 2026commit 9c9ad88b6003 (bcgit/bc-java)
Fix landed in bcgit/bc-java commit 9c9ad88b6003 — awaiting tagged release
https://github.com/bcgit/bc-java/commit/9c9ad88b6003bb6230d2434bd892cc1e95b294e4CVE‐2026‐18036 · bcgit/bc-java Wiki · GitHub
https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9018036Vendor Advisories for CVE-2026-18036(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 04:33 UTCGHSA enrichment
- 2026-10-03 17:11 UTCEG score recompute
- 2026-10-03 17:10 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 05:45 UTCGHSA enrichment
- 2026-10-02 18:20 UTCEG score recompute
- 2026-10-02 18:20 UTCGHSA enrichment
- 2026-10-02 18:20 UTCGHSA enrichment
- 2026-10-02 17:47 UTCEG score recompute
- 2026-10-02 17:47 UTCGHSA enrichment
- 2026-10-02 14:45 UTCGHSA enrichment
- 2026-10-02 08:27 UTCEG score recompute
- 2026-10-02 07:57 UTCEG score recompute
- 2026-10-02 07:55 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-18036?
When was CVE-2026-18036 disclosed?
Is CVE-2026-18036 actively exploited?
What is the CVSS score of CVE-2026-18036?
How do I remediate CVE-2026-18036?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18036
Is Your Infrastructure Affected by CVE-2026-18036?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.