CVE-2026-41458

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS

Also known asEUVD-2026-24587 (ENISA EUVD) · GHSA-rvqf-8mp6-8qjg (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

OwnTone Server versions 28.4 through 29.0 contain a race condition vulnerability in the DAAP login handler that allows unauthenticated attackers to crash the server by exploiting unsynchronized access to the global DAAP session list. Attackers can flood the DAAP /login endpoint with concurrent requests to trigger a remote denial of service condition without requiring authentication.

CVSS
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.4%
EPSS %ILE
30th
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.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: 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

April 22, 2026

Last Modified

November 8, 2026

Advisory Details (3)

Auto-updated May 4, 2026
Fix referenced — no release confirmed yet.
Web page

OwnTone Server < 29.1 Race Condition DoS via DAAP Login | Advisories | VulnCheck

https://www.vulncheck.com/advisories/owntone-server-race-condition-dos-via-daap-login
Web page

[daap] Fix session list race during concurrent logins by yhcho0405 · Pull Request #1980 · owntone/owntone-server · GitHub

https://github.com/owntone/owntone-server/pull/1980
Web page

[daap] Fix session list race during concurrent logins · owntone/owntone-server@dca9464 · GitHub

https://github.com/owntone/owntone-server/commit/dca94641a5ed66500822dd51281774794cdb6c22

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 36× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 269 rows 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 169 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-41458?
CVE-2026-41458 is a high-severity vulnerability; its CVE record was published on April 22, 2026. OwnTone Server versions 28.4 through 29.0 contain a race condition vulnerability in the DAAP login handler that allows unauthenticated attackers to crash the server by exploiting unsynchronized access to the global DAAP session list. Attackers can flood the DAAP /login endpoint with concurrent…
When was CVE-2026-41458 made public?
CVE-2026-41458 was made public on March 8, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on April 22, 2026. EchelonGraph's copy of the record carries a last-modified date of November 8, 2026; the record at its source may have been updated since.
Is CVE-2026-41458 actively exploited?
CVE-2026-41458 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41458?
CVE-2026-41458 has a CVSS base score of 8.2 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-41458?
A fix for CVE-2026-41458 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41458?

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