# CVE-2026-129358: Linux Foundation Magma NMS routes.ts handleReact cross site scripting

> Remote attackers can inject scripts into the Magma NMS web interface, affecting operators of the network management system.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 15 Nov 2026
- **Also known as:** GHSA-cw9p-3fjg-gh3r

## What is CVE-2026-129358?

CVE-2026-129358 is a medium-severity cross-site scripting vulnerability in Linux Foundation Magma, published on 15 Nov 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability was identified in Linux Foundation Magma up to 1.9.0. Impacted is the function handleReact of the file nms/server/main/routes.ts of the component NMS. Such manipulation leads to cross site scripting. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.

An affected version is exposed as installed. No special setting or call is needed.


Products: Linux Foundation Magma.

CPE match criteria (CPE 2.3):

- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.0 up to 1.0
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.1 up to 1.1
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.2 up to 1.2
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.3 up to 1.3
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.4 up to 1.4
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.5 up to 1.5
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.6 up to 1.6
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.7 up to 1.7
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.8 up to 1.8
- `cpe:2.3:o:linux_foundation:magma:*:*:*:*:*:*:*:*` from 1.9.0 up to 1.9.0

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

No fix has been published for CVE-2026-129358 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129358 being exploited?

There is no known exploitation of CVE-2026-129358 in the wild and no public exploit code.

Public exploit code:

- Magma NMS <=1.9.0 stored XSS: org names stored unvalidated and rendered unescaped (!{configJson}, JSON.stringify leaves <> alone) — an org named xss-</script><script>… executes in every member's browser. Real NMS+Postgres; raw breakout vs u003c-escaped differential; synthetic fixed side. (github_poc): https://github.com/googlesky/CVE-2026-129358

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129358 is a medium-severity cross-site scripting vulnerability in Linux Foundation Magma, published on 15 Nov 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-129358 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Linux Foundation Magma. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-129358/ (Markdown: https://insights.sbomify.com/CVE-2026-129358/index.md)
```

## Sources

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

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