# CVE-2026-5323: priyankark a11y-mcp index.js A11yServer server-side request forgery

> A local attacker can exploit server-side request forgery in the a11y-mcp library to access internal resources or bypass security controls.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-prmx-7v35-7q82

## What is CVE-2026-5323?

CVE-2026-5323 is a medium-severity server-side request forgery vulnerability in priyankark a11y-mcp, published on 2 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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."

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-5323?

2 open source packages ship an affected version, including a11y-mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `a11y-mcp` | npm | All versions | 1.0.5 |
| `a11y-mcp` | npm | All versions | 1.0.5 |

## How do I fix CVE-2026-5323?

Upgrade a11y-mcp to 1.0.5 or later.

## Is CVE-2026-5323 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5323 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5323 and fix it if it is affected.

What it is: CVE-2026-5323 is a medium-severity server-side request forgery vulnerability in priyankark a11y-mcp, published on 2 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5323 exists.

Affected packages and fixed versions:
- a11y-mcp (npm): affected all versions; fixed in 1.0.5
- a11y-mcp (npm): affected all versions; fixed in 1.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5323/ (Markdown: https://insights.sbomify.com/CVE-2026-5323/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5323
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5323
- OSV: https://osv.dev/vulnerability/CVE-2026-5323

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5323/
Summaries are generated and may contain mistakes; the official description above is the record.