CVE-2026-49835

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 62% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.1.0, the global wrapMetrics middleware records raw HTTP request path r.URL.Path and raw HTTP request method r.Method as Prometheus labels for latency and request count metric vectors before routing, allowing an unauthenticated remote attacker to issue requests with random paths such as /api/v1/timestamp/ or random HTTP methods and create unbounded permanent time-series entries that exhaust memory. This issue is fixed in version 2.1.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v2.1.0

Patch available: sigstore/timestamp-authority v2.1.0

https://github.com/sigstore/timestamp-authority/releases/tag/v2.1.0
github_commit

commit 506ec57b6ac2 (sigstore/timestamp-authority)

Fix landed in sigstore/timestamp-authority commit 506ec57b6ac2 — awaiting tagged release

https://github.com/sigstore/timestamp-authority/commit/506ec57b6ac2ea1e4739322e47453469425b69b5
github Patch Available

OOM due to unbounded metric label cardinality · Advisory · sigstore/timestamp-authority · GitHub

https://github.com/sigstore/timestamp-authority/security/advisories/GHSA-9c54-x2g4-v92j

Vendor Advisories for CVE-2026-49835(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/sigstore/timestamp-authority———
github.com/sigstore/timestamp-authority/v2—2.1.0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-sigstore-timestamp-authority1.2.3-2 ... 2.1.3-2 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-sigstore-timestamp-authority1.2.3-2, 1.2.9-1, 2.0.3-1, 2.0.3-2, 2.0.4-12.1.0-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:48 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 00:47 UTCEG score recompute
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:09 UTCEG score recompute
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 14:35 UTCEG score recompute
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 18:01 UTCEG score recompute
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 22:41 UTCEG score recompute
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 68 more
  1. 2026-08-24 23:52 UTCEG score recompute
  2. 2026-08-24 11:39 UTCEG score recompute
  3. 2026-08-23 08:52 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 08:20 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 05:59 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 05:30 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 23:00 UTCEG score recompute
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 05:03 UTCEG score recompute
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 01:17 UTCEG score recompute
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 13:03 UTCEG score recompute
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 12:36 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-13 23:55 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 23:27 UTCEG score recompute
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 23:00 UTCEG score recompute
  26. 2026-08-11 10:46 UTCEG score recompute
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-09 22:06 UTCEG score recompute
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-08 21:40 UTCEG score recompute
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-07 21:12 UTCEG score recompute
  33. 2026-08-06 20:45 UTCEG score recompute
  34. 2026-08-06 13:47 UTCEPSS rescore
  35. 2026-08-05 20:18 UTCEG score recompute
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 17:27 UTCEG score recompute
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-04 10:39 UTCEPSS rescore
  40. 2026-08-03 16:53 UTCEG score recompute
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-02 04:12 UTCEG score recompute
  43. 2026-08-02 02:27 UTCEPSS rescore
  44. 2026-08-01 15:58 UTCEG score recompute
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-31 02:57 UTCEG score recompute
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 14:40 UTCEG score recompute▲ 1.60
  49. 2026-07-30 14:27 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  50. 2026-07-30 13:11 UTCEG score recompute
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-29 13:44 UTCEG score recompute
  53. 2026-07-28 15:37 UTCEPSS rescore
  54. 2026-07-28 14:19 UTCEG score recompute
  55. 2026-07-27 13:15 UTCEG score recompute
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 13:51 UTCEG score recompute
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 14:18 UTCEPSS rescore
  60. 2026-07-23 14:18 UTCEPSS rescore
  61. 2026-07-23 03:18 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescore
  63. 2026-07-21 15:25 UTCEPSS rescore
  64. 2026-07-20 17:08 UTCEPSS rescore
  65. 2026-07-19 14:31 UTCEPSS rescore
  66. 2026-07-19 14:31 UTCEPSS rescore
  67. 2026-07-19 02:29 UTCEPSS rescore
  68. 2026-06-30 19:31 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49835?
CVE-2026-49835 is a high vulnerability published on June 30, 2026. Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.1.0, the global wrapMetrics middleware records raw HTTP request path r.URL.Path and raw HTTP request method r.Method as Prometheus labels for latency and request count metric vectors before routing, allowing an…
When was CVE-2026-49835 disclosed?
CVE-2026-49835 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49835 actively exploited?
CVE-2026-49835 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.8% of all scored CVEs.
What is the CVSS score of CVE-2026-49835?
CVE-2026-49835 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-49835?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49835, 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-49835

Explore →

Is Your Infrastructure Affected by CVE-2026-49835?

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

Start Free Scan →Browse All CVEs