CVE-2026-22703

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.2%
KEV
Not listed

Published

January 10, 2026

Last Modified

February 5, 2026

References (3)

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/sigstore/cosign———
github.com/sigstore/cosign/v2—2.6.2—
github.com/sigstore/cosign/v3—3.0.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:06 UTCEG score recompute
  2. 2026-07-19 02:29 UTCEPSS rescore
  3. 2026-07-19 02:28 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 17:03 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-08 15:15 UTCEPSS rescore
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 06:02 UTCOSV refresh
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 15:06 UTCEPSS rescore
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 32 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-17 17:35 UTCOSV refresh
  6. 2026-06-16 17:52 UTCEPSS rescore
  7. 2026-06-15 17:48 UTCEPSS rescore
  8. 2026-06-14 23:18 UTCEPSS rescore
  9. 2026-06-12 23:12 UTCEPSS rescore
  10. 2026-06-10 22:18 UTCEPSS rescore
  11. 2026-06-10 13:22 UTCEPSS rescore
  12. 2026-06-08 14:17 UTCEPSS rescore
  13. 2026-06-08 14:17 UTCEPSS rescore
  14. 2026-06-07 15:25 UTCEPSS rescore
  15. 2026-06-07 15:24 UTCEPSS rescore
  16. 2026-06-05 22:47 UTCEPSS rescore
  17. 2026-06-05 06:10 UTCEPSS rescore
  18. 2026-06-05 06:10 UTCEPSS rescore
  19. 2026-06-04 13:12 UTCEPSS rescore
  20. 2026-06-04 13:12 UTCEPSS rescore
  21. 2026-06-04 13:12 UTCEPSS rescore
  22. 2026-06-02 20:13 UTCEPSS rescore
  23. 2026-06-02 20:13 UTCEPSS rescore
  24. 2026-06-01 13:51 UTCEPSS rescore
  25. 2026-06-01 13:51 UTCEPSS rescore
  26. 2026-06-01 13:51 UTCEPSS rescore
  27. 2026-05-31 00:16 UTCEPSS rescore
  28. 2026-05-31 00:16 UTCEPSS rescore
  29. 2026-05-31 00:16 UTCEPSS rescore
  30. 2026-05-29 16:20 UTCEG score recompute
  31. 2026-05-29 13:44 UTCEPSS rescore
  32. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-22703?
CVE-2026-22703 is a medium vulnerability published on January 10, 2026. Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor…
When was CVE-2026-22703 disclosed?
CVE-2026-22703 was first published in the National Vulnerability Database on January 10, 2026, with the most recent update on February 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22703 actively exploited?
CVE-2026-22703 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22703?
CVE-2026-22703 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-22703?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22703, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-22703

Explore →

Is Your Infrastructure Affected by CVE-2026-22703?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs