CVE-2026-22772
cosign: github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary
CVE-2026-22772 is fixed in 6 products on 1 platform, first by DEBIAN-CVE-2026-22772, released January 12, 2026. It is not reported as exploited. Patch Radar priority: Routine.
Routine
CVSS
5.3
medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0023
14th percentile
github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| cosign · opensuse-leap 15.6 | 3.0.5-150400.3.35.1 | SUSE-SU-2026:0777-1 | Mar 3, 2026 |
| cosign · opensuse-leap 16.0 | 3.0.5-160000.1.1 | OPENSUSE-SU-2026:20386-1 | Mar 18, 2026 |
| cosign · sles 15.7 | 3.0.5-150400.3.35.1 | SUSE-SU-2026:0777-1 | Mar 3, 2026 |
| cosign · sles 16.0 | 3.0.5-160000.1.1 | SUSE-SU-2026:20904-1 | Mar 18, 2026 |
| golang-github-sigstore-fulcio · Debian 14 | 1.8.5-1 | DEBIAN-CVE-2026-22772 | Jan 12, 2026 |
| govulncheck-vulndb · opensuse-leap 15.6 | 0.0.20260123T022811-150000.1.140.1 | SUSE-SU-2026:0292-1 | Jan 26, 2026 |
| govulncheck-vulndb · opensuse-leap 16.0 | 0.0.20260723T184607-160000.1.1 | OPENSUSE-SU-2026:21483-1 | Jul 30, 2026 |
| hauler · opensuse-leap 16.0 | 1.4.1-bp160.1.1 | OPENSUSE-RU-2026:20161-1 | Jan 27, 2026 |
| runfinch-finch · amzn 2023 | 1.15.1-1.amzn2023.0.1 | ALAS2023-2026-1507 | Mar 30, 2026 |
| vexctl · opensuse-leap 15.6 | 0.4.1+git78.f951e3a-150000.1.11.1 | SUSE-SU-2026:0592-1 | Feb 20, 2026 |
| vexctl · opensuse-leap 16.0 | 0.4.4+git20.5d61136-160000.1.1 | OPENSUSE-SU-2026:21481-1 | Jul 30, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.