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

SUSE · Security update for google-cloud-sap-agent

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

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 google-cloud-sap-agent fixes the following issues - CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265764). - CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266604). Changes for google-cloud-sap-agent: - Update to version 3.15 * Remove LoggingClient error failure for hanadiskrestore and hanadiskbackup. * Add checks for unexpected arguments in hanadiskbackup and hanadiskrestore. * Update SAP Agent version to 3.15. * Refactor grubBootLoaderX5 to check for BLS support via grub2-mkconfig help. * Update all go dependencies * Check grub2-mkconfig for BLS support on X4 instances. * Add tenant SID collection to supportbundle. * Update golang.org/x/net dependency. This is to address (#444) * Fork tuned.conf to tuned-x5.conf for X5 series configurations * Enable configureX5 in configureinstance. * Create skeleton implementation and tests for X5 configureinstance support. * Enable detection of x5 machine types in configureinstance - Update to version 3.14 (bsc#1265991) * Update Daemon Restart method to pass the correct cancel function to the new handler. * Remove redundant error logging in HANA disk restore. * Fetch and rename Logical Volume during HANA disk restore. * Add usage metrics for CMEK disk restore. * Add multi-region and global KMS keys location checks. * Convert HANA SID to uppercase in hanadiskbackup and hanadiskrestore. * Log warning instead of erroring out on KMS key get failure. * Initialize GCE client in status onetime command. * Validate presence of KMS key in hanadiskrestore. * Add SID parameter to HANA backup/restore path functions. * Add KMS key location validation for HANA disk restore. * Update agent version to 3.14. * Fixes an issue if there is a whitespace around an argument passed in * Add validation to prevent using both CSEK and KMS keys in hanadiskrestore. * Handle disk recreation in HANA disk restore when IOPS, throughput, size, or KMS key are specified. * Refactor disk restore and configuration logic. * Add support for CMEK encryption of restored disks. * Remove obsolete TODOs. - Update to version 3.13 * Replace strings.TrimSuffix with strings.TrimSpace in hanabackup.go * Improve error messages in hanabackup.go. * Add system state logging and logical device verification. * Minor version bump * Improve SAP instance comparison for process metrics collectors to prevent unnecessary restarts of collectors. * Delete supportbundlehandler package. * Remove configurehandler from sapguestactions. * Delete hanadiskbackuphandler from sapguestactions. * Remove Guest Actions and GCBDR Actions from initial daemon start. * Remove `gsutil` check from collection definition. * Delete performancediagnosticshandler package. * Remove unused handlers and shell command execution. * status feature fixes - pass secret name * Fix an issue in system discovery if discovering a network fails, particularly due to an IAM permission error. * Add verification for HANA data volume state after disk restore. * Error handling for rescanVolumegroups and improved logging. * Add link to What's New page in the sapagent README. * Add secret manager IAM checks if secret key is preset in status

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