CVE-2026-49419

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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: cisa-adp, epss
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

When the JAIL_AT_DESC flag is specified, kern_jail_set() and kern_jail_get() released the reference to the caller's current prison before looking up the jail descriptor. If the descriptor lookup failed, error-handling paths released the same reference a second time.

An unprivileged local user can trigger a prison reference count underflow, which may cause the prison structure to be freed while still in use. When this is done on the jail host, the bug will generally result in an immediate panic. However, if the user is running in a jail, then it may be possible to exploit the bug to elevate privileges.

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

Published

August 19, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-49419(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 14× in last 7d / 14× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 19:18 UTCGHSA enrichment
  3. 2026-08-20 18:52 UTCEG score recompute 8.80
  4. 2026-08-20 18:52 UTCGHSA enrichment
  5. 2026-08-20 18:51 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  6. 2026-08-20 04:20 UTCGHSA enrichment
  7. 2026-08-20 04:19 UTCNVD update
  8. 2026-08-20 04:08 UTCEG score recompute
  9. 2026-08-20 04:08 UTCGHSA enrichment
  10. 2026-08-20 04:07 UTCMITRE cvelistV5
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 05:19 UTCNVD update
  13. 2026-08-19 04:44 UTCEG score recompute
  14. 2026-08-19 04:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-49419?
CVE-2026-49419 is a high vulnerability published on August 19, 2026. When the JAILATDESC flag is specified, kernjailset() and kernjailget() released the reference to the caller's current prison before looking up the jail descriptor. If the descriptor lookup failed, error-handling paths released the same reference a second time. An unprivileged local user can trigger…
When was CVE-2026-49419 disclosed?
CVE-2026-49419 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49419 actively exploited?
CVE-2026-49419 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 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-49419?
CVE-2026-49419 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49419, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49419?

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