CVE-2026-86231

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-09-07. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A security flaw has been discovered in mwiede jsch up to 2.28.5. Affected is the function getRevokedKeys of the file src/main/java/com/jcraft/jsch/KnownHosts.java. Performing a manipulation of the argument known_hosts results in improper check for certificate revocation. The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitability is told to be difficult. The exploit has been released to the public and may be used for attacks. Upgrading to version 2.28.6 is able to address this issue. The patch is named 194a2f76a5c0f1c3f778565be3fd66bcafc42d23. You should upgrade the affected component.

CVSS v3
3.7
EG Score
3.7(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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
Severity37% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 6, 2026

Last Modified

September 11, 2026

References (9)

Vendor Advisories for CVE-2026-86231(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 27× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 05:06 UTCEG score recompute
  3. 2026-09-18 05:06 UTCGHSA enrichment
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 14:09 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 01:15 UTCEG score recompute
  10. 2026-09-15 01:15 UTCGHSA enrichment
  11. 2026-09-11 21:24 UTCEG score recompute
  12. 2026-09-11 21:24 UTCGHSA enrichment
  13. 2026-09-11 21:20 UTCNVD updateCVSS v4 → 2.9
  14. 2026-09-11 20:47 UTCEG score recompute
  15. 2026-09-11 20:47 UTCGHSA enrichment
  16. 2026-09-11 20:43 UTCMITRE cvelistV5CVSS v4 → 6.3
  17. 2026-09-11 17:59 UTCEG score recompute
  18. 2026-09-11 17:59 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-08 22:01 UTCEPSS rescore
  22. 2026-09-08 14:07 UTCEG score recompute
  23. 2026-09-08 14:07 UTCGHSA enrichment
  24. 2026-09-06 23:32 UTCEG score recompute
  25. 2026-09-06 23:32 UTCNVD updateCVSS v4 → 2.9
Show 2 more
  1. 2026-09-06 22:48 UTCEG score recompute
  2. 2026-09-06 22:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86231?
CVE-2026-86231 is a low vulnerability published on September 6, 2026. A security flaw has been discovered in mwiede jsch up to 2.28.5. Affected is the function getRevokedKeys of the file src/main/java/com/jcraft/jsch/KnownHosts.java. Performing a manipulation of the argument known_hosts results in improper check for certificate revocation. The attack is possible to…
When was CVE-2026-86231 disclosed?
CVE-2026-86231 was first published in the National Vulnerability Database on September 6, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86231 actively exploited?
CVE-2026-86231 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.1% of all scored CVEs.
What is the CVSS score of CVE-2026-86231?
CVE-2026-86231 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-86231?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86231, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-86231?

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

Start Free Scan →Browse All CVEs