CVE-2025-12977

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-11-24. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-198811 (ENISA EUVD) · GHSA-v498-rhc6-28g9 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs. An attacker with network access or the ability to write records into Splunk or Elasticsearch can supply tag_key values containing special characters such as newlines or ../ that are treated as valid tags. Because tags influence routing and some outputs derive filenames or contents from tags, this can allow newline injection, path traversal, forged record injection, or log misrouting, impacting data integrity and log routing.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 24, 2025

Last Modified

October 18, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
Patch available.

Vendor Advisories for CVE-2025-12977(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 237 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 01:50 UTCEG score recompute
  2. 2026-10-31 01:50 UTCVendor advisory
  3. 2026-10-31 01:50 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  5. 2026-10-30 01:51 UTCEG score recompute
  6. 2026-10-30 01:51 UTCVendor advisory
  7. 2026-10-30 01:51 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-29 01:52 UTCEG score recompute
  10. 2026-10-29 01:52 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-10-28 01:52 UTCEG score recompute
  13. 2026-10-28 01:51 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  15. 2026-10-27 01:49 UTCEG score recompute
  16. 2026-10-27 01:48 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-10-25 21:51 UTCVendor advisory
  19. 2026-10-25 21:51 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-25 16:47 UTCEG score recompute
  21. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  22. 2026-10-24 21:49 UTCEG score recompute
  23. 2026-10-24 21:49 UTCVendor advisory
  24. 2026-10-24 21:49 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 73 more
  1. 2026-10-23 21:50 UTCEG score recompute
  2. 2026-10-23 21:50 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-10-22 21:49 UTCEG score recompute
  5. 2026-10-22 21:49 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-21 21:50 UTCEG score recompute
  8. 2026-10-21 21:50 UTCVendor advisory
  9. 2026-10-21 21:50 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-10-20 21:23 UTCEG score recompute
  12. 2026-10-20 21:23 UTCVendor advisory
  13. 2026-10-20 21:23 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-19 21:20 UTCEG score recompute
  16. 2026-10-19 21:20 UTCVendor advisory
  17. 2026-10-19 21:20 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-18 20:28 UTCEG score recompute
  20. 2026-10-18 20:28 UTCVendor advisory
  21. 2026-10-18 20:28 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  23. 2026-10-18 05:50 UTCEG score recompute
  24. 2026-10-17 22:16 UTCEG score recompute
  25. 2026-10-17 22:16 UTCVendor advisory
  26. 2026-10-17 22:15 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  28. 2026-10-16 22:14 UTCEG score recompute
  29. 2026-10-16 22:14 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  31. 2026-10-15 18:51 UTCEG score recompute
  32. 2026-10-15 18:51 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  33. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  34. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  35. 2026-10-14 12:31 UTCEG score recompute
  36. 2026-10-14 12:30 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  37. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  38. 2026-10-13 12:28 UTCVendor advisory
  39. 2026-10-13 12:28 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  40. 2026-10-12 17:24 UTCEG score recompute
  41. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  42. 2026-10-12 12:25 UTCVendor advisory
  43. 2026-10-12 12:24 UTCGHSA enrichmentGHSA-v498-rhc6-28g9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  44. 2026-10-11 20:55 UTCEG score recompute
  45. 2026-10-11 19:05 UTCEG score recompute
  46. 2026-10-11 15:46 UTCEG score recompute
  47. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  48. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  49. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  50. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  51. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  52. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  53. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  54. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  55. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  56. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  57. 2026-10-01 10:40 UTCOSV refresh
  58. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  59. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  60. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  61. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  62. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  63. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  64. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  65. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  66. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  67. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  68. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  69. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  70. 2026-09-12 10:10 UTCOSV refresh
  71. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  72. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  73. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile

Frequently asked(5)

What is CVE-2025-12977?
CVE-2025-12977 is a critical-severity vulnerability; its CVE record was published on November 24, 2025. Fluent Bit inhttp, insplunk, and inelasticsearch input plugins fail to sanitize tagkey inputs. An attacker with network access or the ability to write records into Splunk or Elasticsearch can supply tag_key values containing special characters such as newlines or ../ that are treated as valid tags.…
When was the CVE record for CVE-2025-12977 published?
The CVE record for CVE-2025-12977 was published on November 24, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 18, 2026; the record at its source may have been updated since.
Is CVE-2025-12977 actively exploited?
CVE-2025-12977 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-12977?
CVE-2025-12977 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-12977?
A fix for CVE-2025-12977 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-12977 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-12977

Explore →

Is Your Infrastructure Affected by CVE-2025-12977?

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