CVE-2026-23991
go-tuf affected by client DoS via malformed server response
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
5.9
go-tuf affected by client DoS via malformed server response
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
- Record
CVE-2026-23991- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-617, CWE-754
- Updated
- 2026-11-02
EUVDEUVD-2026-3673
5.9
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
- Record
EUVD-2026-3673- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-846p-jg2w-w324
5.9
go-tuf affected by client DoS via malformed server response
Security Disclosure: Client DoS via malformed server response
Summary
If the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a DoS. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key.
Impact
Client crashes upon receiving and parsing malformed TUF metadata. This can cause long running services to enter an restart/crash loop.
Workarounds
None currently.
Affected code
The metadata.checkType function did not properly type assert the (untrusted) input causing it to panic on malformed data.
- Record
GHSA-846p-jg2w-w324- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-617, CWE-754
- Updated
- 2026-11-02
NVD
5.9
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
- Record
CVE-2026-23991- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-617, CWE-754
- Updated
- 2026-11-02
OSVBELL-CVE-2026-23991
7.5
- Record
BELL-CVE-2026-23991- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSV
5.9
go-tuf affected by client DoS via malformed server response
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
- Record
CVE-2026-23991- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-617, CWE-754
- Updated
- 2026-11-02
Show 12 moreShow less
OSVDEBIAN-CVE-2026-23991
7.5
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
- Record
DEBIAN-CVE-2026-23991- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVGHSA-846p-jg2w-w324
5.9
go-tuf affected by client DoS via malformed server response
Security Disclosure: Client DoS via malformed server response
Summary
If the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a DoS. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key.
Impact
Client crashes upon receiving and parsing malformed TUF metadata. This can cause long running services to enter an restart/crash loop.
Workarounds
None currently.
Affected code
The metadata.checkType function did not properly type assert the (untrusted) input causing it to panic on malformed data.
- Record
GHSA-846p-jg2w-w324- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-617, CWE-754
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-23991
5.9
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
- Record
UBUNTU-CVE-2026-23991- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVAZL-75186 No score
CVE-2026-23991 affecting package gh for versions less than 2.62.0-13
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.
- Record
AZL-75186- Updated
- 2026-11-02
OSVGO-2026-4348 No score
Client DoS via malformed server response in github.com/theupdateframework/go-tuf
Client DoS via malformed server response in github.com/theupdateframework/go-tuf
- Record
GO-2026-4348- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10235-1 No score
cosign-3.0.5-1.1 on GA media
These are all security issues fixed in the cosign-3.0.5-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10235-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20386-1 No score
Security update for cosign
This update for cosign fixes the following issues:
Update to version 3.0.5:
- CVE-2026-24122: Fixed improper validation of certificates that outlive expired CA certificates (bsc#1258542)
- CVE-2026-26958: Fixed filippo.io/edwards25519: failure to initialize receiver in MultiScalarMult can produce invalid results and lead to undefined behavior (bsc#1258612)
- CVE-2026-24137: Fixed github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1257139)
- CVE-2026-22772: Fixed github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services (bsc#1256562)
- CVE-2026-23991: Fixed github.com/theupdateframework/go-tuf/v2: denial of service due to invalid TUF metadata JSON returned by TUF repository (bsc#1257080)
- CVE-2026-23992: Fixed github.com/theupdateframework/go-tuf/v2: unauthorized modification to TUF metadata files due to a compromised or misconfigured TUF repository (bsc#1257085)
- CVE-2025-11065: Fixed github.com/go-viper/mapstructure/v2: sensitive Information leak in logs (bsc#1250620)
- CVE-2026-22703: Fixed that cosign verification accepts any valid Rekor entry under certain conditions (bsc#1256496)
- CVE-2025-58181: Fixed golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253913)
- Record
openSUSE-SU-2026:20386-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0403-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20260205T172317 2026-02-05T17:23:17Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4337 CVE-2025-68121
- GO-2026-4357 CVE-2026-23954 GHSA-7f67-crqm-jgh7
- GO-2026-4359 CVE-2026-23953 GHSA-x6jc-phwx-hp32
- GO-2026-4395 CVE-2026-25499 GHSA-gwch-7m8v-7544
- GO-2026-4396 CVE-2026-25059 GHSA-qmj2-8r24-xxcq
- GO-2026-4397 CVE-2026-25060 GHSA-wf93-3ghh-h389
- GO-2026-4398 GHSA-grh9-37g7-53mj
- GO-2026-4403 CVE-2025-22873
- GO-2026-4404 CVE-2025-70849 GHSA-mw8w-q3f7-2v85
- GO-2026-4405 CVE-2026-25121 GHSA-5g94-c2wx-8pxw
- GO-2026-4406 CVE-2026-25122 GHSA-6p9p-q6wh-9j89
- GO-2026-4407 CVE-2026-24843 GHSA-qxx2-7h4c-83f4
- GO-2026-4408 CVE-2026-24844 GHSA-vqqr-rmpc-hhg2
- GO-2026-4409 CVE-2026-25145 GHSA-2w4f-9fgg-q2v9
- GO-2026-4411 CVE-2026-25579 GHSA-hrr4-3wgr-68x3
- GO-2026-4412 CVE-2026-25143 GHSA-rf4g-89h5-crcr
- GO-2026-4413 CVE-2026-25578 GHSA-rh3r-8pxm-hg4w
- GO-2026-4414 CVE-2026-25160 GHSA-8jmm-3xwx-w974
- GO-2026-4415 CVE-2026-25161 GHSA-x4q4-7phh-42j9
- GO-2026-4416 CVE-2026-25538 GHSA-8wpc-j9q9-j5m2
- GO-2026-4417 CVE-2026-24514 GHSA-2pf9-vr92-6h3v
- GO-2026-4418 CVE-2023-43631 GHSA-3mq9-xhgq-r7gj
- GO-2026-4419 CVE-2026-24513 GHSA-4g2f-xcph-2335
- GO-2026-4421 CVE-2026-24735 GHSA-5w5r-8xc6-2xhw
- GO-2026-4422 CVE-2023-43632 GHSA-6jp5-grgh-jw42
- GO-2026-4423 CVE-2026-1580 GHSA-9h3p-52vh-959w
- GO-2026-4425 CVE-2025-62878 GHSA-jr3w-9vfr-c746
- GO-2026-4426 CVE-2026-24512 GHSA-jx8c-56mg-h6vp
- GO-2026-4428 CVE-2023-43633 GHSA-4c4v-42hc-72p6
- GO-2026-4430 CVE-2023-43630 GHSA-phcg-h58r-gmcq
- GO-2026-4432 CVE-2023-43634 GHSA-wc42-fcjp-v8vq
- GO-2026-4433 CVE-2025-61732
- GO-2026-4440 CVE-2025-47911
- GO-2026-4441 CVE-2025-58190
-
Update to version 0.0.20260204T190754 2026-02-04T19:07:54Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4324 CVE-2026-23645 GHSA-pcjq-j3mq-jv5j
- GO-2026-4327 CVE-2026-23742 GHSA-cc8m-98fm-rc9g
- GO-2026-4329 CVE-2026-21696 GHSA-2497-gp99-2m74
- GO-2026-4330 CVE-2026-22822 GHSA-77v3-r3jw-j2v2
- GO-2026-4331 CVE-2025-69199 GHSA-8w7m-w749-rx98
- GO-2026-4333 CVE-2026-23829 GHSA-54wq-72mp-cq7c
- GO-2026-4334 CVE-2026-23517 GHSA-4r5r-ccr6-q6f6
- GO-2026-4335 CVE-2026-23518 GHSA-63m5-974w-448v
- GO-2026-4336 CVE-2026-22808 GHSA-gfpw-jgvr-cw4j
- GO-2026-4343 CVE-2026-23847 GHSA-w836-5gpm-7r93
- GO-2026-4344 CVE-2026-23849 GHSA-43mm-m3h2-3prc
- GO-2026-4345 CVE-2026-23845 GHSA-6jxm-fv7w-rw5j
- GO-2026-4346 CVE-2026-23851 GHSA-94c7-g2fj-7682
- GO-2026-4347 CVE-2026-23850 GHSA-cv54-7wv7-qxcw
- GO-2026-4348 CVE-2026-23991 GHSA-846p-jg2w-w324
- GO-2026-4349 CVE-2026-23992 GHSA-fphv-w9fq-2525
- GO-2026-4350 CVE-2026-23960 GHSA-cv78-6m8q-ph82
- GO-2026-4351 CVE-2026-23990 GHSA-4xh5-jcj2-ch8q
- GO-2026-4352 GHSA-r92c-9c7f-3pj8
- GO-2026-4353 CVE-2026-24058 GHSA-pchf-49fh-w34r
- GO-2026-4354 CVE-2026-23831 GHSA-273p-m2cw-6833
- GO-2026-4355 CVE-2026-24117 GHSA-4c4x-jm2x-pf9j
- GO-2026-4356 CVE-2026-24124 GHSA-j8hf-cp34-g4j7
- GO-2026-4362 CVE-2026-20800 GHSA-2vgv-hgv4-22mh
- GO-2026-4363 CVE-2026-20897 GHSA-393c-qgvj-3xph
- GO-2026-4364 CVE-2026-20912 GHSA-4xx9-vc8v-87hv
- GO-2026-4365 CVE-2026-0798 GHSA-8fwc-qjw5-rvgp
- GO-2026-4366 CVE-2026-20888 GHSA-9cgq-wp42-4rpq
- GO-2026-4367 CVE-2026-20736 GHSA-hgr3-x44x-33hx
- GO-2026-4368 CVE-2026-20883 GHSA-j8xr-c56q-m8jj
- GO-2026-4369 CVE-2026-20904 GHSA-qqgv-v353-cv8p
- GO-2026-4370 CVE-2026-20750 GHSA-rw22-5hhq-pfpf
- GO-2026-4377 CVE-2026-24686 GHSA-jqc5-w2xx-5vq4
- GO-2026-4378 CVE-2026-24470 GHSA-mxxc-p822-2hx9
- GO-2026-4379 CVE-2026-24738 GHSA-j49h-6577-5xwq
- GO-2026-4380 CVE-2026-24740 GHSA-m855-r557-5rc5
- GO-2026-4381 CVE-2026-22039 GHSA-8p9x-46gm-qfx2
- GO-2026-4382 CVE-2026-23881 GHSA-r2rj-wwm5-x6mq
- GO-2026-4384…
- Record
SUSE-SU-2026:0403-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0757-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Update to version 0.0.20260226T182644 2026-02-26T18:26:44Z (jsc#PED-11136) Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-4259 CVE-2025-13767 GHSA-fmqf-pmcm-8cx9
- GO-2025-4260 CVE-2025-64641 GHSA-vww6-79rv-3j4x
- GO-2026-4282 CVE-2017-18873 GHSA-x6mw-hf2j-vqpc
- GO-2026-4305 CVE-2017-18903 GHSA-fcwg-45jh-5qhf
- GO-2026-4325 CVE-2025-14822 GHSA-9r42-rhw3-2222
- GO-2026-4326 CVE-2025-14435 GHSA-mx8m-v8qm-xwr8
- GO-2026-4332 CVE-2026-23644 GHSA-2657-3c98-63jq
- GO-2026-4348 CVE-2026-23991 GHSA-846p-jg2w-w324
- GO-2026-4349 CVE-2026-23992 GHSA-fphv-w9fq-2525
- GO-2026-4377 CVE-2026-24686 GHSA-jqc5-w2xx-5vq4
- GO-2026-4410 CVE-2026-25140 GHSA-f4w5-5xv9-85f6
- GO-2026-4502 CVE-2026-25766 GHSA-pgvm-wxw2-hrv9
- GO-2026-4534 CVE-2026-25899 GHSA-2mr3-m5q5-wgp6
- GO-2026-4535 CVE-2026-27585 GHSA-4xrr-hq4w-6vf4
- GO-2026-4536 CVE-2026-27590 GHSA-5r3v-vc8m-m96g
- GO-2026-4537 CVE-2026-27589 GHSA-879p-475x-rqh2
- GO-2026-4538 CVE-2026-27587 GHSA-g7pc-pc7g-h8jh
- GO-2026-4539 CVE-2026-27586 GHSA-hffm-g8v7-wrv7
- GO-2026-4540 CVE-2026-25891 GHSA-m3c2-496v-cw3v
- GO-2026-4541 CVE-2026-27588 GHSA-x76f-jf84-rqj8
- GO-2026-4543 CVE-2026-25882 GHSA-mrq8-rjmw-wpq3
- GO-2026-4559 CVE-2026-27141
Update to version 0.0.20260225T230704 2026-02-25T23:07:04Z.
- GO-2026-4358 CVE-2026-24137 GHSA-fcv2-xgw5-pqxf
- GO-2026-4361 GHSA-c32p-wcqj-j677
- GO-2026-4394 CVE-2026-24051 GHSA-9h8m-3fm2-qjrq
- GO-2026-4399 CVE-2026-25518 GHSA-gx3x-vq4p-mhhv
- GO-2026-4507 CVE-2026-26314 GHSA-2gjw-fg97-vg3r
- GO-2026-4508 CVE-2026-26313 GHSA-689v-6xwf-5jf3
- GO-2026-4509 CVE-2026-27017 GHSA-7m29-f4hw-g2vx
- GO-2026-4511 CVE-2026-26315 GHSA-m6j8-rg6r-7mv8
- GO-2026-4512 CVE-2026-26995 GHSA-rrxv-pmq9-x67r
- GO-2026-4531 CVE-2026-25591 GHSA-w6x6-9fp7-fqm4
- GO-2026-4532 CVE-2026-25802 GHSA-299v-8pq9-5gjq
- GO-2026-4533 CVE-2026-27571 GHSA-qrvq-68c2-7grw
- GO-2026-4542 CVE-2026-27598 GHSA-6v48-fcq6-ff23
- GO-2026-4545 CVE-2025-50180 GHSA-3c9r-837r-qqm4
- GO-2026-4546 CVE-2026-27611 GHSA-8vrh-3pm2-v4v6
- GO-2026-4547 CVE-2026-27626 GHSA-49gm-hh7w-wfvf
- GO-2026-4548 GHSA-2phg-qgmm-r638
Update to version 0.0.20260223T182315 2026-02-23T18:23:15Z.
- GO-2026-4392 CVE-2026-24845 GHSA-9m43-p3cx-w8j5
- GO-2026-4434 CVE-2023-43635 GHSA-4jvr-vj2c-8q37
- GO-2026-4435 CVE-2023-43636 GHSA-5h7v-g49c-h887
- GO-2026-4436 CVE-2023-43637 GHSA-g7vp-j25f-h34p
- GO-2026-4442 GHSA-x9p2-77v6-6vhf
- GO-2026-4444 CVE-2026-23989 GHSA-9j2f-3rj3-wgpg
- GO-2026-4445 CVE-2026-25760 GHSA-2286-hxv5-cmp2
- GO-2026-4446 CVE-2026-24851 GHSA-jq9f-gm9w-rwm9
- GO-2026-4447 GHSA-vf5j-r2hw-2hrw
- GO-2026-4448 CVE-2025-64111 GHSA-gg64-xxr9-qhjp
- GO-2026-4449 CVE-2025-64175 GHSA-p6x6-9mx6-26wj
- GO-2026-4450 CVE-2026-23632 GHSA-5qhx-gwfj-6jqr
- GO-2026-4451 CVE-2026-22592 GHSA-cr88-6mqm-4g57
- GO-2026-4452 CVE-2026-24135 GHSA-jp7c-wj6q-3qf2
- GO-2026-4453 CVE-2026-23633 GHSA-mrph-w4hh-gx3g
- GO-2026-4454 GHSA-26gq-grmh-6xm6
- GO-2026-4455 CVE-2025-70963 GHSA-9f8m-9547-2gqm
- GO-2026-4456 CVE-2025-13523 GHSA-ffx7-34p2-vm3w
- GO-2026-4457 CVE-2025-65852 GHSA-rjv5-9px2-fqw6
- GO-2026-4458 CVE-2026-25793 GHSA-69x3-g4r3-p962
- GO-2026-4459 CVE-2017-18907 GHSA-42x9-rr3c-gr59
- GO-2026-4460 CVE-2017-18918 GHSA-5ghq-28r7-qwfj
- GO-2026-4461 CVE-2026-25804 GHSA-86x4-wp9f-wrr9
- GO-2026-4462 CVE-2017-18915 GHSA-hxxj-8phw-74vw
- GO-2026-4463 CVE-2017-18917 GHSA-jxc4-w54c-qv5r
- GO-2026-4464 CVE-2017-18911 GHSA-m462-mqw4-2c8m
- GO-2026-4465 GHSA-vhvq-fv9f-wh4q
- GO-2026-4466 CVE-2026-25791 GHSA-wxrw-gvg8-fqjp
- GO-2026-4467 CVE-2017-18916 GHSA-x33g-375j-jhf7
- GO-2026-4471 CVE-2025-66630 GHSA-68rr-p4fp-j59v
- GO-2026-4473 CVE-2026-25934 GHSA-37cx-329c-33x3
- GO-2026-4474 CVE-2026-25890 GHSA-4mh3-h929-w968
- GO-2026-4475 CVE-2026-25889 GHSA-hxw8-4h9j-hq2r
- GO-2026-4476 CVE-2017-18908…
- Record
SUSE-SU-2026:0757-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0777-1 No score
Security update for cosign
This update for cosign fixes the following issues:
Update to version 3.0.5 (jsc#SLE-23879).
Security issues fixed:
- CVE-2025-11065: github.com/go-viper/mapstructure/v2: sensitive Information leak in logs (bsc#1250620).
- CVE-2025-58181: golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253913).
- CVE-2026-22703: Verification accepts any valid Rekor entry under certain conditions (bsc#1256496).
- CVE-2026-22772: github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services (bsc#1256562).
- CVE-2026-23991: github.com/theupdateframework/go-tuf/v2: denial of service due to invalid TUF metadata JSON returned by TUF repository (bsc#1257080).
- CVE-2026-23992: github.com/theupdateframework/go-tuf/v2: unauthorized modification to TUF metadata files due to a compromised or misconfigured TUF repository (bsc#1257085).
- CVE-2026-24122: improper validation of certificates that outlive expired CA certificates (bsc#1258542).
- CVE-2026-24137: github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1257139).
- CVE-2026-26958: filippo.io/edwards25519: failure to initialize receiver in MultiScalarMult can produce invalid results and lead to undefined behavior (bsc#1258612).
Other updates and bugfixes:
- chore(deps): bump google.golang.org/api from 0.260.0 to 0.264.0 (#4679)
- chore(deps): bump github.com/sigstore/rekor-tiles/v2 from 2.0.1 to 2.1.0 (#4670)
- chore(deps): bump filippo.io/edwards25519 from 1.1.0 to 1.1.1 (#4712)
- chore(deps): bump gitlab.com/gitlab-org/api/client-go (#4680)
- chore(deps): bump the gomod group across 1 directory with 4 updates (#4702)
- chore(deps): bump the actions group with 3 updates (#4703)
- update golang builder to use go1.25.7 (#4687)
- update golangci-lint to v2.8.x (#4688)
- Support DSSE signing conformance test (#4685)
- chore(deps): bump the actions group across 1 directory with 8 updates (#4689)
- Deprecate rekor-entry-type flag (#4691)
- Deprecate cosign triangulate (#4676)
- Deprecate cosign copy (#4681)
- Enforce TSA requirement for Rekor v2, Fuclio signing (#4683)
- chore(deps): bump github.com/theupdateframework/go-tuf/v2 (#4668)
- chore(deps): bump golang from 1.25.5 to 1.25.6 in the all group (#4673)
- Automatically require signed timestamp with Rekor v2 entries (#4666)
- Fix syntax issue in conformance test, update nightly (#4664)
- Add mTLS support for TSA client connections when signing with a signing config (#4620)
- fix: avoid panic on malformed tlog entry body (#4652)
- Verify validity of chain rather than just certificate (#4663)
- Allow --local-image with --new-bundle-format for v2 and v3 signatures (#4626)
- chore(deps): bump the gomod group across 1 directory with 3 updates (#4662)
- Bump sigstore/sigstore to resolve GHSA (#4660)
- Gracefully fail if bundle payload body is not a string (#4648)
- fix: avoid panic on malformed replace payload (#4653)
- chore(deps): bump github.com/sigstore/rekor from 1.4.3 to 1.5.0 (#4659)
- fix: avoid panic on malformed attestation payload (#4651)
- fix: avoid panic on malformed tlog entries (#4649)
- Update conformance to latest
- docs(cosign): clarify RFC3161 revocation semantics (#4642)
- Add empty predicate to cosign sign when payload type is application/vnd.in-toto+json (#4635)
- chore(deps): bump github.com/sigstore/fulcio from 1.8.4 to 1.8.5 (#4637)
- Add origin key for ctfe trusted root
- Add changelog updates for v3.0.4 and v2.6.2 (#4625)
- Update to version 3.0.4:
- Fix bundle verify path for old bundle/trusted root (#4623)
- chore(deps): bump gitlab.com/gitlab-org/api/client-go (#4616)
- chore(deps): bump cuelang.org/go in the gomod group (#4615)
- Optimize cosign tree performance by caching digest resolution (#4612)
- Don't require a trusted root to verify offline with a key (#4613)
- Support default services for trusted-root and…
- Record
SUSE-SU-2026:0777-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:20904-1 No score
Security update for cosign
This update for cosign fixes the following issues:
Update to version 3.0.5:
- CVE-2026-24122: Fixed improper validation of certificates that outlive expired CA certificates (bsc#1258542)
- CVE-2026-26958: Fixed filippo.io/edwards25519: failure to initialize receiver in MultiScalarMult can produce invalid results and lead to undefined behavior (bsc#1258612)
- CVE-2026-24137: Fixed github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1257139)
- CVE-2026-22772: Fixed github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services (bsc#1256562)
- CVE-2026-23991: Fixed github.com/theupdateframework/go-tuf/v2: denial of service due to invalid TUF metadata JSON returned by TUF repository (bsc#1257080)
- CVE-2026-23992: Fixed github.com/theupdateframework/go-tuf/v2: unauthorized modification to TUF metadata files due to a compromised or misconfigured TUF repository (bsc#1257085)
- CVE-2025-11065: Fixed github.com/go-viper/mapstructure/v2: sensitive Information leak in logs (bsc#1250620)
- CVE-2026-22703: Fixed that cosign verification accepts any valid Rekor entry under certain conditions (bsc#1256496)
- CVE-2025-58181: Fixed golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253913)
- Record
SUSE-SU-2026:20904-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/theupdateframework/go-tuf/v2Go |
before 2.3.1 | 2.3.1 |
ghAzure Linux:3 |
before 2.62.0-13 | 2.62.0-13 |
docker-cli-buildxAlpaquita:stream |
0.11.0-r0 up to 0.32.0-r0 | 0.32.0-r0 |
golang-github-theupdateframework-go-tufDebian:13 |
All versions, plus listed versions 2.0.2+0.7.0-12.3.0+0.7.0-12.4.1+0.7.0-12.4.1+0.7.0-22.4.1+0.7.0-2~exp2.4.2+0.7.0-1 |
None known |
golang-github-theupdateframework-go-tufDebian:14 |
before 2.4.1+0.7.0-1, plus listed versions 2.0.2+0.7.0-12.3.0+0.7.0-1 |
2.4.1+0.7.0-1 |
govulncheck-vulndbopenSUSE:Leap 15.6 From an advisory covering 76 CVEs |
before 0.0.20260205T172317-150000.1.146.1 | 0.0.20260205T172317-150000.1.146.1 |
govulncheck-vulndbopenSUSE:Leap 15.6 From an advisory covering 104 CVEs |
before 0.0.20260226T182644-150000.1.149.1 | 0.0.20260226T182644-150000.1.149.1 |
cosignSUSE:Linux Enterprise Module for Basesystem 15 SP7 From an advisory covering 9 CVEs |
before 3.0.5-150400.3.35.1 | 3.0.5-150400.3.35.1 |
cosignopenSUSE:Leap 15.6 From an advisory covering 9 CVEs |
before 3.0.5-150400.3.35.1 | 3.0.5-150400.3.35.1 |
cosignSUSE:Linux Enterprise Server 16.0 From an advisory covering 9 CVEs |
before 3.0.5-160000.1.1 | 3.0.5-160000.1.1 |
Show 8 moreShow less
| Package | Affected | Fixed |
|---|---|---|
cosignSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 9 CVEs |
before 3.0.5-160000.1.1 | 3.0.5-160000.1.1 |
golang-github-theupdateframework-go-tufUbuntu:24.04:LTS |
All versions, plus listed versions 0.5.2-50.6.1-1 |
None known |
golang-github-theupdateframework-go-tufUbuntu:25.10 |
All versions, plus listed versions 2.0.2+0.7.0-1 |
None known |
golang-github-theupdateframework-go-tufUbuntu:26.10 |
All versions, plus listed versions 2.3.0+0.7.0-12.4.2+0.7.0-1 |
None known |
golang-github-theupdateframework-go-tufUbuntu:26.04:LTS |
All versions, plus listed versions 2.0.2+0.7.0-12.3.0+0.7.0-1 |
None known |
cosignopenSUSE:Tumbleweed From an advisory covering 6 CVEs |
before 3.0.5-1.1 | 3.0.5-1.1 |
cosignopenSUSE:Leap 16.0 From an advisory covering 9 CVEs |
before 3.0.5-160000.1.1 | 3.0.5-160000.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 1734 CVEs |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-23991 is a medium vulnerability (CVSS 5.9) in Theupdateframework Go-tuf, published January 21, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.58%, the 48th percentile. Fixed in github.com/theupdateframework/go-tuf/v2 2.3.1.
References
github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324
github.com/theupdateframework/go-tuf/commit/73345ab6b0eb7e59d525dac17a428f043074cef6
github.com/theupdateframework/go-tuf/releases/tag/v2.3.1
nvd.nist.gov/vuln/detail/CVE-2026-23991
github.com/advisories/GHSA-846p-jg2w-w324
docs.bell-sw.com/security/cves/CVE-2026-23991
Show 194 moreShow less
github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23991.json
security-tracker.debian.org/tracker/CVE-2026-23991
github.com/theupdateframework/go-tuf
suse.com/support/update/announcement/2026/suse-su-20260403-1
suse.com/security/cve/CVE-2023-43630
suse.com/security/cve/CVE-2023-43631
suse.com/security/cve/CVE-2023-43632
suse.com/security/cve/CVE-2023-43633
suse.com/security/cve/CVE-2023-43634
suse.com/security/cve/CVE-2025-14525
suse.com/security/cve/CVE-2025-22873
suse.com/security/cve/CVE-2025-47911
suse.com/security/cve/CVE-2025-58190
suse.com/security/cve/CVE-2025-61732
suse.com/security/cve/CVE-2025-62878
suse.com/security/cve/CVE-2025-67601
suse.com/security/cve/CVE-2025-68121
suse.com/security/cve/CVE-2025-69199
suse.com/security/cve/CVE-2025-69820
suse.com/security/cve/CVE-2025-70849
suse.com/security/cve/CVE-2026-0798
suse.com/security/cve/CVE-2026-1237
suse.com/security/cve/CVE-2026-1580
suse.com/security/cve/CVE-2026-20736
suse.com/security/cve/CVE-2026-20750
suse.com/security/cve/CVE-2026-20800
suse.com/security/cve/CVE-2026-20883
suse.com/security/cve/CVE-2026-20888
suse.com/security/cve/CVE-2026-20897
suse.com/security/cve/CVE-2026-20904
suse.com/security/cve/CVE-2026-20912
suse.com/security/cve/CVE-2026-21696
suse.com/security/cve/CVE-2026-22039
suse.com/security/cve/CVE-2026-22808
suse.com/security/cve/CVE-2026-22822
suse.com/security/cve/CVE-2026-23517
suse.com/security/cve/CVE-2026-23518
suse.com/security/cve/CVE-2026-23645
suse.com/security/cve/CVE-2026-23742
suse.com/security/cve/CVE-2026-23829
suse.com/security/cve/CVE-2026-23831
suse.com/security/cve/CVE-2026-23845
suse.com/security/cve/CVE-2026-23847
suse.com/security/cve/CVE-2026-23849
suse.com/security/cve/CVE-2026-23850
suse.com/security/cve/CVE-2026-23851
suse.com/security/cve/CVE-2026-23881
suse.com/security/cve/CVE-2026-23953
suse.com/security/cve/CVE-2026-23954
suse.com/security/cve/CVE-2026-23960
suse.com/security/cve/CVE-2026-23990
suse.com/security/cve/CVE-2026-23991
suse.com/security/cve/CVE-2026-23992
suse.com/security/cve/CVE-2026-24058
suse.com/security/cve/CVE-2026-24117
suse.com/security/cve/CVE-2026-24124
suse.com/security/cve/CVE-2026-24470
suse.com/security/cve/CVE-2026-24512
suse.com/security/cve/CVE-2026-24513
suse.com/security/cve/CVE-2026-24514
suse.com/security/cve/CVE-2026-24686
suse.com/security/cve/CVE-2026-24735
suse.com/security/cve/CVE-2026-24738
suse.com/security/cve/CVE-2026-24740
suse.com/security/cve/CVE-2026-24748
suse.com/security/cve/CVE-2026-24843
suse.com/security/cve/CVE-2026-24844
suse.com/security/cve/CVE-2026-24846
suse.com/security/cve/CVE-2026-25059
suse.com/security/cve/CVE-2026-25060
suse.com/security/cve/CVE-2026-25121
suse.com/security/cve/CVE-2026-25122
suse.com/security/cve/CVE-2026-25143
suse.com/security/cve/CVE-2026-25145
suse.com/security/cve/CVE-2026-25160
suse.com/security/cve/CVE-2026-25161
suse.com/security/cve/CVE-2026-25499
suse.com/security/cve/CVE-2026-25538
suse.com/security/cve/CVE-2026-25578
suse.com/security/cve/CVE-2026-25579
suse.com/support/update/announcement/2026/suse-su-20260757-1
suse.com/security/cve/CVE-2017-18873
suse.com/security/cve/CVE-2017-18903
suse.com/security/cve/CVE-2017-18906
suse.com/security/cve/CVE-2017-18907
suse.com/security/cve/CVE-2017-18908
suse.com/security/cve/CVE-2017-18909
suse.com/security/cve/CVE-2017-18911
suse.com/security/cve/CVE-2017-18912
suse.com/security/cve/CVE-2017-18915
suse.com/security/cve/CVE-2017-18916
suse.com/security/cve/CVE-2017-18917
suse.com/security/cve/CVE-2017-18918
suse.com/security/cve/CVE-2023-43635
suse.com/security/cve/CVE-2023-43636
suse.com/security/cve/CVE-2023-43637
suse.com/security/cve/CVE-2025-13523
suse.com/security/cve/CVE-2025-13767
suse.com/security/cve/CVE-2025-13821
suse.com/security/cve/CVE-2025-14350
suse.com/security/cve/CVE-2025-14435
suse.com/security/cve/CVE-2025-14573
suse.com/security/cve/CVE-2025-14822
suse.com/security/cve/CVE-2025-50180
suse.com/security/cve/CVE-2025-64111
suse.com/security/cve/CVE-2025-64175
suse.com/security/cve/CVE-2025-64641
suse.com/security/cve/CVE-2025-65852
suse.com/security/cve/CVE-2025-66630
suse.com/security/cve/CVE-2025-67860
suse.com/security/cve/CVE-2025-70963
suse.com/security/cve/CVE-2026-0997
suse.com/security/cve/CVE-2026-0998
suse.com/security/cve/CVE-2026-0999
suse.com/security/cve/CVE-2026-20796
suse.com/security/cve/CVE-2026-21434
suse.com/security/cve/CVE-2026-21435
suse.com/security/cve/CVE-2026-21438
suse.com/security/cve/CVE-2026-22592
suse.com/security/cve/CVE-2026-22892
suse.com/security/cve/CVE-2026-23632
suse.com/security/cve/CVE-2026-23633
suse.com/security/cve/CVE-2026-23644
suse.com/security/cve/CVE-2026-23989
suse.com/security/cve/CVE-2026-24051
suse.com/security/cve/CVE-2026-24122
suse.com/security/cve/CVE-2026-24135
suse.com/security/cve/CVE-2026-24137
suse.com/security/cve/CVE-2026-24834
suse.com/security/cve/CVE-2026-24845
suse.com/security/cve/CVE-2026-24851
suse.com/security/cve/CVE-2026-24894
suse.com/security/cve/CVE-2026-24895
suse.com/security/cve/CVE-2026-25120
suse.com/security/cve/CVE-2026-25140
suse.com/security/cve/CVE-2026-25229
suse.com/security/cve/CVE-2026-25232
suse.com/security/cve/CVE-2026-25242
suse.com/security/cve/CVE-2026-25518
suse.com/security/cve/CVE-2026-25591
suse.com/security/cve/CVE-2026-25760
suse.com/security/cve/CVE-2026-25766
suse.com/security/cve/CVE-2026-25791
suse.com/security/cve/CVE-2026-25793
suse.com/security/cve/CVE-2026-25802
suse.com/security/cve/CVE-2026-25804
suse.com/security/cve/CVE-2026-25882
suse.com/security/cve/CVE-2026-25889
suse.com/security/cve/CVE-2026-25890
suse.com/security/cve/CVE-2026-25891
suse.com/security/cve/CVE-2026-25899
suse.com/security/cve/CVE-2026-25934
suse.com/security/cve/CVE-2026-25935
suse.com/security/cve/CVE-2026-25949
suse.com/security/cve/CVE-2026-26014
suse.com/security/cve/CVE-2026-26055
suse.com/security/cve/CVE-2026-26056
suse.com/security/cve/CVE-2026-26187
suse.com/security/cve/CVE-2026-26190
suse.com/security/cve/CVE-2026-26201
suse.com/security/cve/CVE-2026-26205
suse.com/security/cve/CVE-2026-26313
suse.com/security/cve/CVE-2026-26314
suse.com/security/cve/CVE-2026-26315
suse.com/security/cve/CVE-2026-26957
suse.com/security/cve/CVE-2026-26958
suse.com/security/cve/CVE-2026-26963
suse.com/security/cve/CVE-2026-26995
suse.com/security/cve/CVE-2026-27017
suse.com/security/cve/CVE-2026-27111
suse.com/security/cve/CVE-2026-27112
suse.com/security/cve/CVE-2026-27141
suse.com/security/cve/CVE-2026-27571
suse.com/security/cve/CVE-2026-27585
suse.com/security/cve/CVE-2026-27586
suse.com/security/cve/CVE-2026-27587
suse.com/security/cve/CVE-2026-27588
suse.com/security/cve/CVE-2026-27589
suse.com/security/cve/CVE-2026-27590
suse.com/security/cve/CVE-2026-27598
suse.com/security/cve/CVE-2026-27611
suse.com/security/cve/CVE-2026-27626
suse.com/support/update/announcement/2026/suse-su-20260777-1
bugzilla.suse.com/1250620
bugzilla.suse.com/1253913
bugzilla.suse.com/1256496
bugzilla.suse.com/1256562
bugzilla.suse.com/1257080
bugzilla.suse.com/1257085
bugzilla.suse.com/1257139
bugzilla.suse.com/1258542
bugzilla.suse.com/1258612
ubuntu.com/security/CVE-2026-23991
cve.org/CVERecord?id=CVE-2026-23991
Left out here: 1,559 references and the rest of 4 source descriptions. The JSON record has them.