CVE-2026-56854VulnerabilityPublished 28 Aug 2026Updated 9 Nov 2026

Golang go.crypto: The source-address critical option

Affects golang-go.cryptoSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-46595

Authoritative record:CVE-2026-56854· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 9 Nov 2026, 14:17 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10golang-go.crypto`pkg:deb/ubuntu/golang-go.crypto?arch=source&distro=stonking`Other threats	Affected =1:0.47.0-1 =1:0.55.0-1	Fixed in–
Ubuntu 26.10google-guest-agent`pkg:deb/ubuntu/google-guest-agent?arch=source&distro=stonking`Other threats	Affected =20250506.01-0ubuntu2 =20250506.01-0ubuntu3 =20260819.00+~20260819.00-0ubuntu1	Fixed in–
Ubuntu 26.10snapd`pkg:deb/ubuntu/snapd?arch=source&distro=stonking`Other threats	Affected 2.74.1+ubuntu26.04.4 – 2.77.1+ubuntu26.10.1 5 affected builds	Fixed in–
Ubuntu 26.04 LTSgoogle-guest-agent`pkg:deb/ubuntu/google-guest-agent?arch=source&distro=resolute`Other threats	Affected =20250506.01-0ubuntu1 =20250506.01-0ubuntu2 =20250506.01-0ubuntu2.1	Fixed in–
Ubuntu Pro 26.04 LTSgolang-go.crypto`pkg:deb/ubuntu/golang-go.crypto?arch=source&distro=esm-apps/resolute`Other threats	Affected 1:0.25.0-1 – 1:0.47.0-1ubuntu0.1~esm1 4 affected builds	Fixed in–
Ubuntu 24.04 LTSgoogle-guest-agent`pkg:deb/ubuntu/google-guest-agent?arch=source&distro=noble`Other threats	Affected 20230426.00-0ubuntu3 – 20250116.00-0ubuntu1~24.04.4 16 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been implemented that enforces the source-address critical option check on permissions returned by all authentication callbacks. Users should update to a version of golang-go.crypto that includes this fix. Since specific fixed versions are not provided in the input, verify the vendor advisory or package updates for patched releases before deployment.

Description

A vulnerability in golang-go.crypto allows source-address restrictions set by certain authentication callbacks to be ignored. The source-address critical option was only enforced for PublicKeyCallback and VerifiedPublicKeyCallback, but not for PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, and GSSAPIWithMICConfig.AllowLogin callbacks. This flaw means that source-address restrictions from these callbacks were silently bypassed. The issue has been addressed by applying the source-address check to permissions returned by all authentication callbacks.

Impact

An attacker could bypass source-address restrictions set by certain authentication callbacks, potentially allowing unauthorized access from untrusted remote addresses. The vulnerability has a high severity with a CVSS score of 7.5, indicating a network attack vector with low complexity and no privileges or user interaction required, resulting in high confidentiality impact but no integrity or availability impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 14:17 UTC

Technical details

References

Community reviews

Related threats