Fonoster 0.5.5 before 0.6.1 allows ../ directory traversal to read arbitrary files via the /sounds/:file or /tts/:file VoiceServer endpoint. This occurs in serveFiles in mods/voice/src/utils.ts. NOTE: serveFiles exists in 0.5.5 but not in the next release, 0.6.1.
CVE-2024-43035
MEDIUMNVD 5.85.8
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
Score 5.8 from GitHub Security Advisory (severity: MODERATE) published 2026-03-05. NVD baseline CVSS 5.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Also known asEUVD-2024-55468 (ENISA EUVD) · GHSA-9fv2-c7v6-p45w (GitHub Security Advisories)Source: ENISA EUVD
5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS: 5.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.8
- EG Score
- 5.8MEDIUMmedium confidence
- EG Risk
- 42EG Risk 42/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)Severity58% × 45%Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation2.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 2.4%
- EPSS %ILE
- 84th
- 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 (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 2.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.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 low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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
March 5, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Aug 4, 2026Patch available.
Web page
Fonoster VoiceServer LFI Vulnerability (CVE-2024-43035) - ZeroPath Blog | ZeroPath
https://zeropath.com/blog/fonoster-voiceserver-lfi-vulnerabilityWeb page
fonoster/mods/voice/src/utils.ts at 4a1438d9dedeaf7b2a5b6a50d5e233f994e2b2cf · fonoster/fonoster · GitHub
https://github.com/fonoster/fonoster/blob/4a1438d9dedeaf7b2a5b6a50d5e233f994e2b2cf/mods/voice/src/utils.ts#L66-L70Vendor Advisories for CVE-2024-43035(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | @fonoster/voice @ 0.6.1 (fixes >= 0.5.5, < 0.6.1) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @fonoster/voice | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2024-43035?
CVE-2024-43035 is a medium-severity vulnerability; its CVE record was published on March 5, 2026. Fonoster 0.5.5 before 0.6.1 allows ../ directory traversal to read arbitrary files via the /sounds/:file or /tts/:file VoiceServer endpoint. This occurs in serveFiles in mods/voice/src/utils.ts. NOTE: serveFiles exists in 0.5.5 but not in the next release, 0.6.1.
When was the CVE record for CVE-2024-43035 published?
The CVE record for CVE-2024-43035 was published on March 5, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2024-43035 actively exploited?
CVE-2024-43035 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-43035?
CVE-2024-43035 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2024-43035?
A fix for CVE-2024-43035 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-43035 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-43035
Is Your Infrastructure Affected by CVE-2024-43035?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.