CVE-2026-46458

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

ICU Scandinavia Boomerang is vulnerable to an information disclosure flaw where sensitive credential files are exposed via static HTTP. This allows an unauthenticated remote attacker to retrieve plaintext service account and SMTP credentials by requesting specific XML files from the webroot. This issue has been fixed in version 2.4.18.029

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.4% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jul 15, 2026
Fix named in the CVE record.
Web page

Podatności w oprogramowaniu ICU Scandinavia Boomerang | CERT Polska

https://cert.pl/posts/2026/07/CVE-2026-46458

Vendor Advisories for CVE-2026-46458(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 11× in last 7d / 37× 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 211 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 111 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 0.4% · 27th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-12 16:02 UTCEG score recompute
  4. 2026-10-11 19:45 UTCEG score recompute
  5. 2026-10-11 17:00 UTCEG score recompute
  6. 2026-10-11 14:25 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-01 12:41 UTCEG score recompute
  18. 2026-10-01 12:41 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-09-28 08:46 UTCEG score recompute
  22. 2026-09-28 08:46 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 26th percentile
Show 75 more
  1. 2026-09-24 08:53 UTCEG score recompute
  2. 2026-09-24 08:53 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  3. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-09-23 03:19 UTCEG score recompute
  5. 2026-09-23 03:19 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  6. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-09-18 04:46 UTCEG score recompute
  9. 2026-09-18 04:46 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  10. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-09-14 11:08 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  14. 2026-09-13 23:13 UTCEG score recompute
  15. 2026-09-13 23:13 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  16. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-09-13 07:16 UTCEG score recompute
  18. 2026-09-13 07:16 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  19. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-09-12 13:03 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  21. 2026-09-11 21:46 UTCEG score recompute
  22. 2026-09-11 21:46 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  23. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  26. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  27. 2026-09-08 00:56 UTCEG score recompute
  28. 2026-09-08 00:56 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  31. 2026-09-06 13:29 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  32. 2026-09-05 20:51 UTCEG score recompute
  33. 2026-09-05 20:51 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  34. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  35. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  36. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  37. 2026-08-31 04:06 UTCEG score recompute
  38. 2026-08-31 04:05 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  40. 2026-08-30 16:05 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  41. 2026-08-30 03:54 UTCEG score recompute
  42. 2026-08-30 03:54 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  43. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  44. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  45. 2026-08-28 01:52 UTCEG score recompute
  46. 2026-08-28 01:52 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  47. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  48. 2026-08-27 12:45 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  49. 2026-08-27 00:50 UTCEG score recompute
  50. 2026-08-27 00:49 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  51. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  52. 2026-08-26 12:53 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  53. 2026-08-26 00:59 UTCEG score recompute
  54. 2026-08-26 00:59 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  55. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  56. 2026-08-25 12:08 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  57. 2026-08-25 00:12 UTCEG score recompute
  58. 2026-08-25 00:12 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  59. 2026-08-24 12:17 UTCEG score recompute
  60. 2026-08-24 12:17 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  61. 2026-08-24 00:10 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  62. 2026-08-23 12:15 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  63. 2026-08-23 00:20 UTCEG score recompute
  64. 2026-08-23 00:20 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  65. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  66. 2026-08-22 12:16 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  67. 2026-08-22 00:03 UTCEG score recompute
  68. 2026-08-22 00:03 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  69. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  70. 2026-08-21 12:08 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  71. 2026-08-21 00:13 UTCEG score recompute
  72. 2026-08-21 00:13 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  73. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  74. 2026-08-20 12:16 UTCGHSA enrichmentGHSA-pc6h-25p2-384f · GitHub severity HIGH
  75. 2026-08-20 00:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46458?
CVE-2026-46458 is a high-severity vulnerability; its CVE record was published on July 15, 2026. ICU Scandinavia Boomerang is vulnerable to an information disclosure flaw where sensitive credential files are exposed via static HTTP. This allows an unauthenticated remote attacker to retrieve plaintext service account and SMTP credentials by requesting specific XML files from the webroot. This…
When was CVE-2026-46458 made public?
CVE-2026-46458 was made public on July 15, 2026: that is the date its CVE record's CNA, CERT.PL, gives for when the vulnerability was made public. The CVE record itself was published on July 15, 2026. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-46458 actively exploited?
CVE-2026-46458 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46458?
CVE-2026-46458 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46458?
The CVE record for CVE-2026-46458 names the fix: "This issue has been fixed in version 2.4.18.029". The vendor advisories EchelonGraph has for CVE-2026-46458 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-46458?

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