CVE
Linux Foundation Magma remote access via hard-coded credentials in interceptors.go
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
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.28% · 21st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Linux Foundation Magma contains a hard-coded credentials flaw in its interceptors.go file. A remote attacker can exploit it over the network without logging in, gaining limited ability to read data, change data, or disrupt the service.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129359 (Linux Foundation Magma interceptors.go hard-coded credentials), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129359 (entry last updated 2026-11-15):
Affected:
- Linux Foundation Magma: versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129359 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129359 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/437422
- https://vuldb.com/vuln/437422/cti
- https://vuldb.com/cve/CVE-2026-129359
- https://vuldb.com/submit/1044005
- https://www.linuxfoundation.org/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129359
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129359"}.Public exploit activity
- GitHub PoC repos: 1
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Linux Foundation Magma
1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9.0
Evidence 8
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Other links · 5
- Advisory
- Advisory
- Advisory
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129359
Is CVE-2026-129359 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-129359?
Magma: versions 1.0, 1.1, 1.2, 1.3, 1.4 and 5 more.Source: cve.now feed data