The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, and GSSAPIWithMICConfig.AllowLogin callbacks were not validated against the client's remote address, so a source-address restriction set by those callbacks was silently ignored. The check is now applied to the Permissions returned by any authentication callback.
CVE-2026-56854
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
September 3, 2026
Advisory Details (3)
Auto-updated Aug 28, 2026x/crypto/ssh: source-address restriction bypassed in 5 callback families · Issue #80213 · golang/go · GitHub
https://go.dev/issue/80213Vendor Advisories for CVE-2026-56854(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | cryostat/cryostat-storage-rhel9:4.2.0-22 | 2026-09-16 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-go.crypto | 1:0.10.0-1 ... 1:0.56.0-1 (36 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-go.crypto | 1:0.25.0-1 ... 1:0.56.0-1 (21 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-go.crypto | 1:0.25.0-1 ... 1:0.54.0-1 (19 versions) | 1:0.55.0-1 | — |
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang.org/x/crypto | — | 0.55.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 29× in last 7d / 87× 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-09-19 01:48 UTCEG score recompute
- 2026-09-19 01:48 UTCVendor advisory
- 2026-09-19 01:48 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:07 UTCVendor advisory
- 2026-09-18 13:07 UTCGHSA enrichment
- 2026-09-18 00:26 UTCEG score recompute
- 2026-09-18 00:26 UTCVendor advisory
- 2026-09-18 00:26 UTCGHSA enrichment
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 11:45 UTCGHSA enrichment
- 2026-09-16 23:04 UTCEG score recompute
- 2026-09-16 23:03 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 10:21 UTCEG score recompute
- 2026-09-16 10:21 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 21:40 UTCGHSA enrichment
- 2026-09-15 08:59 UTCEG score recompute
- 2026-09-15 08:59 UTCGHSA enrichment
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-14 20:18 UTCGHSA enrichment
- 2026-09-14 07:37 UTCGHSA enrichment
- 2026-09-13 18:56 UTCEG score recompute
- 2026-09-13 18:56 UTCGHSA enrichment
Show 62 moreShow fewer
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 06:14 UTCGHSA enrichment
- 2026-09-12 17:33 UTCEG score recompute
- 2026-09-12 17:32 UTCGHSA enrichment
- 2026-09-12 04:50 UTCGHSA enrichment
- 2026-09-11 16:09 UTCEG score recompute
- 2026-09-11 16:09 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 03:14 UTCGHSA enrichment
- 2026-09-10 14:33 UTCEG score recompute
- 2026-09-10 14:33 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 01:52 UTCGHSA enrichment
- 2026-09-09 13:10 UTCGHSA enrichment
- 2026-09-09 00:28 UTCEG score recompute
- 2026-09-09 00:28 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 11:13 UTCGHSA enrichment
- 2026-09-07 22:31 UTCEG score recompute
- 2026-09-07 22:31 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 09:49 UTCGHSA enrichment
- 2026-09-06 21:07 UTCEG score recompute
- 2026-09-06 21:07 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 08:23 UTCGHSA enrichment
- 2026-09-05 19:42 UTCEG score recompute
- 2026-09-05 19:42 UTCGHSA enrichment
- 2026-09-05 07:02 UTCGHSA enrichment
- 2026-09-04 18:21 UTCEG score recompute
- 2026-09-04 18:21 UTCGHSA enrichment
- 2026-09-04 05:40 UTCEG score recompute
- 2026-09-04 05:40 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 16:57 UTCGHSA enrichment
- 2026-09-03 09:06 UTCGHSA enrichment
- 2026-09-02 20:24 UTCEG score recompute
- 2026-09-02 20:24 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 04:50 UTCGHSA enrichment
- 2026-09-01 16:07 UTCEG score recompute
- 2026-09-01 16:07 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 02:58 UTCGHSA enrichment
- 2026-08-31 14:17 UTCGHSA enrichment
- 2026-08-31 01:35 UTCEG score recompute
- 2026-08-31 01:35 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 12:54 UTCEG score recompute
- 2026-08-30 12:54 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 00:12 UTCGHSA enrichment
- 2026-08-29 11:31 UTCEG score recompute
- 2026-08-29 11:31 UTCGHSA enrichment
- 2026-08-28 22:48 UTCGHSA enrichment
- 2026-08-28 22:03 UTCEG score recompute▲ 7.50
- 2026-08-28 22:03 UTCGHSA enrichment
- 2026-08-28 21:59 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-08-28 16:29 UTCNVD update
- 2026-08-28 15:30 UTCEG score recompute
- 2026-08-28 15:25 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-56854?
When was CVE-2026-56854 disclosed?
Is CVE-2026-56854 actively exploited?
What is the CVSS score of CVE-2026-56854?
How do I remediate CVE-2026-56854?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56854
Is Your Infrastructure Affected by CVE-2026-56854?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.