CVE-2026-43980

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

Score 6.3 from GitHub Security Advisory published 2026-06-03. the CNA's CVSS baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:github_m, epss, ghsa
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

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

malla: Stored XSS via Meshtastic node names in multiple frontend pages

Node names (long_name, short_name) received via MQTT are stored in SQLite without sanitization and rendered into the DOM without escaping. Any participant on a public Meshtastic MQTT broker can set a malicious node name that executes JavaScript in the browser of every Malla dashboard visitor.

Affected files:

  • src/malla/templates/traceroute_graph.html (line ~832)
  • src/malla/templates/map.html (lines ~945, 1078)
  • src/malla/templates/packet_detail.html (lines ~1402, 1452)
  • src/malla/static/js/relay_node_analysis.js (line ~124)

Steps to reproduce

  • Publish a Meshtastic NODEINFO_APP packet to any public MQTT broker with long_name set to a HTML entity i.e ``
  • Wait for malla-capture to store it
  • Open the dashboard

Impact

Allows unauthenticated remote attackers to execute arbitrary JavaScript in the browser, such as:

  • Phishing overlays
  • Force redirect to malicious websites
  • Injection of arbitrary third-party scripts (no CSP restrictions)
  • Browser resource abuse
  • Persistent dashboard denial of service

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

Published

June 3, 2026

Last Modified

June 3, 2026

Vendor Advisories for CVE-2026-43980(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 / EcosystemFixed in / PatchReleasedSource
pipmalla—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)
PyPI(1)
PackageVulnerable rangeFixed inDependents
malla0.1.0 ... 0.1.7 (8 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× 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-07-28 03:29 UTCGHSA enrichment
  2. 2026-07-26 22:30 UTCEG score recompute
  3. 2026-07-26 22:29 UTCGHSA enrichment
  4. 2026-07-23 03:14 UTCEG score recompute
  5. 2026-07-16 00:27 UTCGHSA enrichment
  6. 2026-07-14 03:26 UTCGHSA enrichment
  7. 2026-07-11 12:35 UTCGHSA enrichment
  8. 2026-07-08 16:18 UTCGHSA enrichment
  9. 2026-07-03 19:36 UTCGHSA enrichment
  10. 2026-07-02 19:48 UTCGHSA enrichment
  11. 2026-07-01 20:49 UTCGHSA enrichment
  12. 2026-06-30 21:50 UTCGHSA enrichment
  13. 2026-06-29 16:35 UTCGHSA enrichment
  14. 2026-06-28 17:43 UTCGHSA enrichment
  15. 2026-06-27 18:49 UTCGHSA enrichment
  16. 2026-06-26 19:58 UTCGHSA enrichment
  17. 2026-06-25 21:07 UTCGHSA enrichment
  18. 2026-06-24 22:16 UTCGHSA enrichment
  19. 2026-06-23 18:58 UTCGHSA enrichment
  20. 2026-06-19 20:32 UTCGHSA enrichment
  21. 2026-06-18 07:46 UTCGHSA enrichment
  22. 2026-06-17 07:53 UTCGHSA enrichment
  23. 2026-06-16 09:01 UTCGHSA enrichment
  24. 2026-06-15 10:07 UTCGHSA enrichment
  25. 2026-06-14 23:18 UTCEPSS rescore
Show 15 more
  1. 2026-06-14 11:16 UTCGHSA enrichment
  2. 2026-06-13 23:00 UTCEPSS rescore
  3. 2026-06-13 12:26 UTCGHSA enrichment
  4. 2026-06-12 23:12 UTCEPSS rescore
  5. 2026-06-12 13:28 UTCGHSA enrichment
  6. 2026-06-11 14:37 UTCGHSA enrichment
  7. 2026-06-10 15:46 UTCGHSA enrichment
  8. 2026-06-09 16:55 UTCGHSA enrichment
  9. 2026-06-08 18:04 UTCGHSA enrichment
  10. 2026-06-07 16:34 UTCGHSA enrichment
  11. 2026-06-06 17:43 UTCGHSA enrichment
  12. 2026-06-05 18:52 UTCGHSA enrichment
  13. 2026-06-04 20:01 UTCGHSA enrichment
  14. 2026-06-03 21:10 UTCEG score recompute
  15. 2026-06-03 21:10 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-43980?
CVE-2026-43980 is a medium vulnerability published on June 3, 2026. malla: Stored XSS via Meshtastic node names in multiple frontend pages Node names (longname, shortname) received via MQTT are stored in SQLite without sanitization and rendered into the DOM without escaping. Any participant on a public Meshtastic MQTT broker can set a malicious node name that…
When was CVE-2026-43980 disclosed?
CVE-2026-43980 was first published in the National Vulnerability Database on June 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43980 actively exploited?
CVE-2026-43980 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 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43980?
CVE-2026-43980 has a CVSS v4.0 base score of 6.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43980?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43980, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43980

Explore →

Is Your Infrastructure Affected by CVE-2026-43980?

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

Start Free Scan →Browse All CVEs