CVE-2026-33186VulnerabilityPublished 8 Jun 2026Updated 10 Nov 2026

SUSE · Security update for elemental-register

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2026-33186· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade SUSE grpc-go to 1.79.3 as a priority.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 3.1 base score

9.1Critical

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

Patch: Available – fixed in 1.79.3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 20 Mar 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 10 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

Upgrade grpc-go and github.com/grpc/grpc-go to 1.79.3.

Affected software

Product	Affected	Fixed in
grpcgrpc-go	Affected <1.79.3	Fixed in 1.79.3
Gogithub.com/grpc/grpc-go`pkg:golang/github.com/grpc/grpc-go`Other threats	Affected <1.79.3	Fixed in 1.79.3

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

Description

This update for elemental-register fixes the following issue - CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2: path pseudo- header (bsc#1260277). Changes: - Update to v1.9.2: * 71d1fb9c Local node labels (#984) * ce6acda9 Bump golang.org/x/net to v0.55.0 includes fixes for: - bsc#1266789 bsc#1265921 bsc#1267197 bsc#1267168 bsc#1251679 * 060958b7 Bump golangci/golangci-lint-action * 3b4b6699 use a real UUID for the machine registration ID * d33faa01 Bump google.golang.org/grpc library (bsc#1260277 CVE-2026-33186) * 6dceb411 Deterministic endpoints for MachineRegistrations (#975) - Update to v1.9.1: * b42116d4 Ensure the machine inventory selector keeps looking for a match - Update to v1.9.0: - Update to v1.9.0-rc1: * 9952ebe1 Update libraries based on dependency scan * 5e128c5d Adapt OBS packages to a 1.9 version to coexist with 1.8 version * f88219af Fix cluster api version in test environment * ad937279 Run 'make generate' to recreate generated code and vendor folder * 15bb505f Bump to cluster API libraries to v1.12.x * 63369022 Bump test environment tools in Makefile * 7b464802 Run 'make vendor' to recreate vendor folder * 879b3464 Bump yip * aeda10ac Fix unit tests after bumping libraries * 33dcb61a Run 'make vendor' to recreate vendor folder * 0ccd96af Bump wrangler from v2 to v3 * ff0190c4 Run 'make generate' to renew all generated code and config files * b28d2f08 Bump controller generator to version 0.19 * 0bf7dc32 Update controller runtime options * 549e720d Run 'make vendor' to recreate vendor folder * 3f0f27e0 Updated cluster-api, steve, rancher/apis, client-go and k8s/api to the level they were at rancher v2.13 * 49ebf0b7 Update headers to 2026 * fd13ba92 Update questions to include SL Micro 6.2

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

Public exploits and detectionGitHub proofs of concept

Technical details

References

Community reviews

Related threats