CVE-2026-72815VulnerabilityPublished 25 Aug 2026Updated 10 Nov 2026

SUSE · Security update for trivy

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-72815· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade SUSE chi to 5.3.0 when convenient.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 4.0 base score

6.9Medium

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

Patch: Available – fixed in 5.3.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 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 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 chi to 5.3.0.

Affected software

Product	Affected	Fixed in
go-chichi	Affected >=5.2.1 <5.3.0	Fixed in 5.3.0
Gogithub.com/go-chi/chi`pkg:golang/github.com/go-chi/chi`Other threats	Affected =5.2.1	Fixed in–

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

Description

This update for trivy fixes the following issue: - CVE-2026-72815,CVE-2026-72816,CVE-2026-72817: github.com/go-chi/chi/v5: multiple IP spoofing vulnerabilities allow authentication bypass, authorization override, and log forgery (bsc#1276128). Changes for trivy: - Update to version 0.74.0: * release: v0.74.0 [main] (#11037) * chore(deps): update golang.org/x modules (#11094) * chore(deps): bump the docker group with 2 updates (#11090) * docs: update release branch ruleset instructions (#11093) * chore(deps): bump the common group across 1 directory with 7 updates (#11086) * fix(misconf): unmark cty values outside the evaluation context (#11078) * chore(deps): bump the aws group across 1 directory with 6 updates (#11053) * fix(misconf): parse Azure flexible server parameters under their own names (#11072) * chore(deps): bump the docker group with 2 updates (#11054) * feat: add RapidFort curated image scanner (#10452) * feat(java): resolve JAR license URLs to SPDX IDs (Bundle-License, pom <url>) (#10948) * refactor(misconf): remove unused Azure expression-related code (#10637) * fix(server): preserve check aliases and query in uploaded blobs (#11080) * fix(java): read artifact properties only from the MANIFEST.MF main section (#11066) * fix(terraform): support OpenTofu language block (#10923) * chore(deps): bump github.com/go-git/go-git/v5 from 5.19.1 to 5.19.2 (#11063) * ci: trigger Auto Ready for Review after Test docs (#11045) * docs: remove trivy-checks from AWS ECR locations (#11044) * refactor(ubuntu): move EOL version resolution out of loop (#11047) * fix(python): normalize dependency names in PEP 621 pyproject.toml (#11050) * chore(deps): bump oras.land/oras-go/v2 from 2.6.1 to 2.6.2 (#11042) * chore(deps): bump github.com/nikolalohinski/gonja/v2 to v2.9.0 (#11038) * fix(terraform): avoid panic when for_each local has unknown object values (#11019) * chore(deps): bump the github-actions group across 2 directories with 15 updates (#11028) * ci(spdx): migrate to Slack notifications (#11032) * ci(helm): bump Trivy version to 0.73.0 for Trivy Helm Chart 0.25.0 (#11034) - Update to version 0.73.0: * release: v0.73.0 [main] (#11012) * docs: clarify debug logs when version check or telemetry is disabled (#10984) * feat(java): support user-defined Maven mirrors in trivy.yaml (#11006) * chore(deps): bump the common group across 1 directory with 17 updates (#11025) * chore(deps): bump the docker group across 1 directory with 2 updates (#10991) * chore(deps): bump the aws group across 1 directory with 6 updates (#10947) * refactor(alpine): remove type assertion when reading the APKINDEX archive (#11013) * chore(deps): bump google.golang.org/grpc from 1.81.1 to 1.82.1 (#10995) * feat(vex): discover OpenVEX in generic in-toto OCI referrers (#10986) * refactor(vuln): add OS.Supplier field and unify supplier terminology (#11007) * chore(deps): bump github.com/google/cel-go from 0.28.1 to 0.30.0 (#11009) * fix(vex): reject non-local VEX repository names (#10987) * fix(vex): handle 304 status code (#10307) * fix(vuln): don't skip packages covered by a driver's own advisory feed (#10980) * fix(conda): avoid panic on an all-operator dependency line (#10955) * chore: add schema id (#10969) * feat(vex): native discovery of VEX documents stored as OCI artifacts (#10932) * feat: add bounded read helpers (#10974) * fix(dotnet): identify deps.json root project from dependency graph (#10954) * feat(java): read Jenkins plugin manifest licenses (#10939) * docs: ask contributors to coordinate before starting on an issue (#10940) * fix(nodejs): support pnpm workspaces with overlapping packages (#10894) * ci: create release branch with the App token to bypass the merge queue rule (#10931) * chore(deps): bump the common group across 1 directory with 15 updates (#10892) * feat(seal): detect no-prefix packages by version suffix (#10911) * chore(deps): bump the testcontainers group with 2 updates (#10918) * chore(deps): bump the docker group across 1 directory with 4 updates (#10919) * fix(java): set per-file digest for nested JARs (#10855) * fix(misconf): guard nil Healthcheck when building Dockerfile from history (#10899) * ci(helm): bump Trivy version to 0.72.0 for Trivy Helm Chart 0.24.0 (#10908) * ci(helm): allow trivy team to approve Chart.yaml bumps (#10912)

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