CVE-2026-49422

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
8.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (FreeBSD) lists FreeBSD versions 15.1-RELEASE up to but not including p1, 15.0-RELEASE up to but not including p11, 14.4-RELEASE up to but not including p7 and 14.3-RELEASE up to but not including p16 as affected. No release containing a fix is confirmed on record.

The RACK setsockopt(2) handler drops the connection lock in order to copy option data from userspace, then reacquires the lock. After reacquiring, it verifies that the TCP stack had not been switched away, but did not reload its pointer to the stack's per-connection control block. If userspace switches stacks twice during this window, the check will succeed but the saved pointer will refer to freed memory.

The bug may be exploitable by an unprivileged local user to escalate privileges.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
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 (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

August 19, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
No fix on record yet.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 48× 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.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-18 03:34 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-17 11:58 UTCEG score recompute
  6. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-12 16:00 UTCEG score recompute
  12. 2026-10-11 19:43 UTCEG score recompute
  13. 2026-10-11 16:57 UTCEG score recompute
  14. 2026-10-11 14:21 UTCEG score recompute
  15. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-08 08:53 UTCEG score recompute
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-06 21:24 UTCEG score recompute
  22. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-10-06 08:02 UTCEG score recompute
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-05 09:38 UTCEG score recompute
Show 75 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-03 17:00 UTCEG score recompute
  3. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-03 00:43 UTCEG score recompute
  5. 2026-10-01 22:50 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-09-30 21:04 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-09-30 08:53 UTCEG score recompute
  10. 2026-09-28 21:45 UTCEG score recompute
  11. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-09-27 19:29 UTCEG score recompute
  13. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-09-27 07:16 UTCEG score recompute
  15. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-09-25 01:14 UTCEG score recompute
  18. 2026-09-24 00:52 UTCEG score recompute
  19. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-23 00:31 UTCEG score recompute
  21. 2026-09-22 00:07 UTCEG score recompute
  22. 2026-09-20 23:36 UTCEG score recompute
  23. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-19 22:46 UTCEG score recompute
  25. 2026-09-18 21:56 UTCEG score recompute
  26. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-17 21:35 UTCEG score recompute
  28. 2026-09-16 20:08 UTCEG score recompute
  29. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-09-16 07:02 UTCEG score recompute
  31. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-15 05:49 UTCEG score recompute
  33. 2026-09-12 16:35 UTCEG score recompute
  34. 2026-09-11 16:13 UTCEG score recompute
  35. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-09-10 15:41 UTCEG score recompute
  37. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-09-09 02:44 UTCEG score recompute
  39. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-09-08 03:57 UTCEG score recompute
  41. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-09-07 00:45 UTCEG score recompute
  43. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-09-06 00:23 UTCEG score recompute
  45. 2026-09-04 23:57 UTCEG score recompute
  46. 2026-09-04 10:39 UTCEG score recompute
  47. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-09-01 20:24 UTCEG score recompute
  49. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-09-01 08:24 UTCEG score recompute
  51. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-08-31 03:26 UTCEG score recompute
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-08-30 03:04 UTCEG score recompute
  55. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-08-29 02:38 UTCEG score recompute
  57. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-08-27 19:13 UTCEG score recompute
  59. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-08-25 18:41 UTCEG score recompute
  61. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  62. 2026-08-24 18:15 UTCEG score recompute
  63. 2026-08-23 05:42 UTCEG score recompute
  64. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  65. 2026-08-22 05:21 UTCEG score recompute
  66. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  67. 2026-08-21 04:58 UTCEG score recompute
  68. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  69. 2026-08-20 01:35 UTCEG score recompute
  70. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  71. 2026-08-19 12:18 UTCEG score recomputeFirst assessed: 8.4 HIGH
  72. 2026-08-19 12:17 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  73. 2026-08-19 06:21 UTCNVD update
  74. 2026-08-19 05:39 UTCEG score recompute
  75. 2026-08-19 05:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-49422?
CVE-2026-49422 is a high-severity vulnerability; its CVE record was published on August 19, 2026. The RACK setsockopt(2) handler drops the connection lock in order to copy option data from userspace, then reacquires the lock. After reacquiring, it verifies that the TCP stack had not been switched away, but did not reload its pointer to the stack's per-connection control block. If userspace…
When was CVE-2026-49422 made public?
CVE-2026-49422 was made public on June 30, 2026: that is the date its CVE record's CNA, FreeBSD, gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-49422 actively exploited?
CVE-2026-49422 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49422?
CVE-2026-49422 has a CVSS v3.1 base score of 8.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49422?
No fix for CVE-2026-49422 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (FreeBSD) lists FreeBSD versions 15.1-RELEASE up to but not including p1, 15.0-RELEASE up to but not including p11, 14.4-RELEASE up to but not including p7 and 14.3-RELEASE up to but not including p16 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49422

Explore →

Is Your Infrastructure Affected by CVE-2026-49422?

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