CVE-2026-24122VulnerabilityPublished 7 Sep 2026Updated 17 Sep 2026

SUSE trivy · Security update for trivy

Affects SUSE trivySource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-24122· Low 3.7

Not known to be exploited · CVSS 3.7 Low.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

3.7Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 19 Feb 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 31 Oct 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
SUSEsuse/trivy`pkg:rpm/suse/trivy`Other threats	Affected =0.74.0-160000.2.1	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 security update for Trivy has been released that addresses all listed vulnerabilities. Users should apply this update promptly to remediate these issues. No additional mitigation steps are indicated beyond applying the official update.

Description

This security update for the Trivy tool addresses multiple vulnerabilities across several dependencies, including improper certificate validation, HTTP method override bypass, denial of service via oversized inputs, information disclosure through crafted tarball hardlinks, authentication bypass and deadlocks in SSH libraries, authorization bypass due to header case mismatches, heap memory exhaustion, and denial of service from missing headers in gRPC servers. These issues collectively pose risks ranging from low to potentially higher impact depending on context. The update fixes these issues to improve overall security.

Impact

The vulnerabilities fixed in this update can lead to various impacts including improper certificate validation potentially undermining trust, bypass of access controls allowing unauthorized actions, denial of service conditions via resource exhaustion or crashes, information disclosure through crafted inputs, and authentication bypass or deadlocks affecting SSH connections. The severity of these impacts varies by vulnerability but collectively they represent significant security risks if left unpatched.

Summary

The update for Trivy fixes several vulnerabilities: CVE-2026-24122 involves improper validation of certificates that outlive expired CA certificates in the cosign package; CVE-2026-37236 allows clients to override HTTP methods via the X-HTTP-Method-Override header, bypassing access control in grpc-gateway; CVE-2026-41178 permits denial of service through oversized baggage headers in OpenTelemetry; CVE-2026-50163 enables information disclosure and arbitrary file access via crafted tarball hardlinks in oras-go; CVE-2026-56854, CVE-2026-56855, and CVE-2026-78662 relate to authentication bypass and deadlocks in the golang.org/x/crypto/ssh library; CVE-2026-84303 allows bypass of authorization policies due to header case handling in grpc-go; CVE-2026-84304 causes heap memory exhaustion via HTTP/2 DATA frame fragmentation in grpc-go; and CVE-2026-84445 leads to denial of service from missing :authority and Host headers in gRPC-Go xDS servers. These vulnerabilities affect multiple components used by Trivy and have been addressed in this update.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:05 UTC

Technical details

References

Community reviews

Related threats