CVE-2026-18036

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG 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 computed
Severity82% × 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, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 9c9ad88b6003 (bcgit/bc-java)

Fix landed in bcgit/bc-java commit 9c9ad88b6003 — awaiting tagged release

https://github.com/bcgit/bc-java/commit/9c9ad88b6003bb6230d2434bd892cc1e95b294e4
generic

CVE‐2026‐18036 · bcgit/bc-java Wiki · GitHub

https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9018036

Vendor 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.

  1. 2026-10-04 04:33 UTCGHSA enrichment
  2. 2026-10-03 17:11 UTCEG score recompute
  3. 2026-10-03 17:10 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 05:45 UTCGHSA enrichment
  6. 2026-10-02 18:20 UTCEG score recompute
  7. 2026-10-02 18:20 UTCGHSA enrichment
  8. 2026-10-02 18:20 UTCGHSA enrichment
  9. 2026-10-02 17:47 UTCEG score recompute
  10. 2026-10-02 17:47 UTCGHSA enrichment
  11. 2026-10-02 14:45 UTCGHSA enrichment
  12. 2026-10-02 08:27 UTCEG score recompute
  13. 2026-10-02 07:57 UTCEG score recompute
  14. 2026-10-02 07:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18036?
CVE-2026-18036 is a high vulnerability published on October 2, 2026. 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…
When was CVE-2026-18036 disclosed?
CVE-2026-18036 was first published on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18036 actively exploited?
CVE-2026-18036 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18036?
CVE-2026-18036 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18036?
An upstream fix for CVE-2026-18036 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-18036 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18036

Explore →

Is Your Infrastructure Affected by CVE-2026-18036?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.