# CVE-2026-129359: Linux Foundation Magma interceptors.go hard-coded credentials

> Remote attackers can use hard-coded credentials in Magma's registry interceptor to access the registry; Magma operators should care.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** Yes
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 15 Nov 2026
- **Also known as:** GHSA-vw3f-m846-9r2c

## What is CVE-2026-129359?

CVE-2026-129359 is a medium-severity hardcoded credentials vulnerability in Linux Foundation Magma, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in Linux Foundation Magma up to 1.9.0. The affected element is an unknown function of the file orc8r/lib/go/registry/interceptors.go. Performing a manipulation results in hard-coded credentials. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.

Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.


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-129359?

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

## Is CVE-2026-129359 being exploited?

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

Public exploit code:

- Magma orc8r <=1.9.0: the public constant 7ZZXAF7CAETF241KL22B8YRR7B5UF401 in x-magma-client-cert-serial is accepted by the real identity interceptor with zero verification — internal-cloud trust for any caller. Real v1.9.0 component; synthetic one-line fixed side (no upstream fix). (github_poc): https://github.com/googlesky/CVE-2026-129359

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129359 is a medium-severity hardcoded credentials vulnerability in Linux Foundation Magma, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129359 in the wild and no public exploit code.
Exposure: Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.

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

## Sources

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

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