Summary
This update for trivy fixes the following issues:
Update to version 0.76.2.
Security issues fixed:
- CVE-2026-97045: golang.org/x/net/html: missing checks during ancestor namespace transitions when rendering raw
text can cause parser differentials (bsc#1289868).
- CVE-2026-116585,CVE-2026-116586,CVE-2026-116587: github.com/go-jose/go-jose/v4: multiple security issues in
github.com/go-jose/go-jose before 4.1.6 (bsc#1288377).
Other updates and bugfixes:
- Update `x/sys` to 0.50.0 to fix ppc64le syscall handling regression.
- Version 0.76.2:
* fix(deps): bump `golang.org/x/net` from 0.61.0 to 0.62.0 [backport: release/v0.76] (#11554)
* chore(deps): bump the common group across 1 directory with 14 updates [backport: release/v0.76] (#11555)
* fix(deps): bump `github.com/go-jose/go-jose/v4` from 4.1.5 to 4.1.6 [backport: release/v0.76] (#11553)
* fix(deps): bump `alpine` to 3.24.3 in container images [backport: release/v0.76] (#11551)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | trivy | 0.76.2-160000.1.1 |
Vulnerabilities 4
-
High 7.5
Go JOSE: DoS when parsing JWKs that contain RSA keys
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.6, go-jose parses attacker-c…
-
Medium 6.9
Go JOSE: Panic during CBC-HMAC processing
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.5, decrypting untrusted JWE …
-
Medium 6.9
Go JOSE: Panics in JSON parsing
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.5, parsing attacker-controll…
-
Medium 6.1
Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once an HTML integration point was found. However, that integration point may itself be a descendant of an element that was foster-parented into a foreign name…