CVE-2026-48939

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

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

Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-07-10), indicating real-world exploitation has been confirmed by US federal agencies. The CNA's CVSS baseline 10.0 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekExploited in the wild
10.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 20%CVSS: 10.0Exploit: Public PoCExposed services: Not assessed

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

A vulnerability in the iCagenda extension for Joomla allows the upload of arbitrary files in the file attachment feature, ultimately resulting in PHP code upload and execution.

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
100
EG Risk 100/100

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 (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (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 sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
EPSS PROB
20%
EPSS %ILE
97th
KEV
⚠ Exploited

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable yes (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)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (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

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://www.icagenda.com/#download · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-48939

Published

June 20, 2026

Last Modified

August 12, 2026

Advisory Details (6)

Auto-updated Oct 7, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet.
Web page

iCagenda - Events Management for Joomla!

https://www.icagenda.com/
Web page

iCagenda - iCagenda 4.0.8 (Security Release)

https://www.icagenda.com/docs/changelog/icagenda-4-0-8
Web page

iCagenda - iCagenda 3.9.15 (Security Release Joomla 3)

https://www.icagenda.com/docs/changelog/icagenda-3-9-15
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-48939
Web page

iCagenda Zero Day File Upload RCE Fixed in 4.0.8 | mySites.guru

https://mysites.guru/blog/icagenda-zero-day-file-upload-rce/
Web page

GitHub - Polosss/By-Poloss..-..CVE-2026-48939: iCagenda Unauthenticated File Upload to RCE · GitHub

https://github.com/Polosss/By-Poloss..-..CVE-2026-48939

Vendor Advisories for CVE-2026-48939(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 46× in last 7d / 217× 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 100 of 823 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. None are among the latest 100 rows. The 723 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Nucleihttp/cves/2026/CVE-2026-48939.yaml
    Published Aug 6, 2026

    Joomla iCagenda < 3.9.10 - Unauthenticated Arbitrary File Upload RCE

    Open source ↗
  • GitHub PoCshinthink/CVE-2026-48939
    Published Jul 5, 2026

    Pre-auth arbitrary file upload RCE exploit for iCagenda Joomla extension < 4.0.8 (CVSS 10.0)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2026-48939?
CVE-2026-48939 is a critical-severity vulnerability; its CVE record was published on June 20, 2026. A vulnerability in the iCagenda extension for Joomla allows the upload of arbitrary files in the file attachment feature, ultimately resulting in PHP code upload and execution.
When was the CVE record for CVE-2026-48939 published?
The CVE record for CVE-2026-48939 was published on June 20, 2026. 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 August 12, 2026; the record at its source may have been updated since.
Is CVE-2026-48939 actively exploited?
Yes. CISA added CVE-2026-48939 to the Known Exploited Vulnerabilities catalog on July 10, 2026, affecting iCagenda iCagenda. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2026-48939?
CVE-2026-48939 has a CVSS base score of 10.0 (the CNA's own assessment, by joomla; NVD's own analysis pending).
Which products are affected by CVE-2026-48939?
CVE-2026-48939 affects iCagenda iCagenda.
How do I remediate CVE-2026-48939?
No fix for CVE-2026-48939 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 vendor advisories EchelonGraph has for CVE-2026-48939 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48939?

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

Book a Demo →Browse All CVEs