CVE-2026-5323

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

A vulnerability was found in priyankark a11y-mcp up to 1.0.5. This vulnerability affects the function A11yServer of the file src/index.js. The manipulation results in server-side request forgery. The attack must be initiated from a local position. The exploit has been made public and could be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. Upgrading to version 1.0.6 is able to resolve this issue. The patch is identified as e3e11c9e8482bd06b82fd9fced67be4856f0dffc. It is recommended to upgrade the affected component. The vendor acknowledged the issue but provides additional context for the CVSS rating: "a11y-mcp is a local stdio MCP server - it has no HTTP endpoint and is not network-accessible. The caller is always the local user or an LLM acting on their behalf with user approval."

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 2, 2026

Last Modified

April 29, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🟡 PoC Available

Server-Side Request Forgery Vulnerability in a11y-mcp · Issue #17 · wing3e/public_exp · GitHub

https://github.com/wing3e/public_exp/issues/17
github_commit

commit e3e11c9e8482 (priyankark/a11y-mcp)

Fix landed in priyankark/a11y-mcp commit e3e11c9e8482 — awaiting tagged release

https://github.com/priyankark/a11y-mcp/commit/e3e11c9e8482bd06b82fd9fced67be4856f0dffc
generic

GitHub - priyankark/a11y-mcp: An MCP (Model Context Protocol) server for performing accessibility audits on webpages using axe-core. Use the results in an agentic loop with your favorite AI assistants (Amp/Cline/Cursor/GH Copilot) and let them fix a11y issues for you! · GitHub

https://github.com/priyankark/a11y-mcp/

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
a11y-mcp—1.0.5—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 23× 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.

Showing the most recent 100 of 136 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5323?
CVE-2026-5323 is a medium vulnerability published on April 2, 2026. A vulnerability was found in priyankark a11y-mcp up to 1.0.5. This vulnerability affects the function A11yServer of the file src/index.js. The manipulation results in server-side request forgery. The attack must be initiated from a local position. The exploit has been made public and could be used.…
When was CVE-2026-5323 disclosed?
CVE-2026-5323 was first published in the National Vulnerability Database on April 2, 2026, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5323 actively exploited?
CVE-2026-5323 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-5323?
CVE-2026-5323 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-5323?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5323, 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-5323

Explore →

Is Your Infrastructure Affected by CVE-2026-5323?

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

Start Free Scan →Browse All CVEs