Back Redpacketsecurity CVE Alert: CVE-2026-129360 – Linux Foundation
A weakness has been identified in Linux Foundation Magma up to 1.9.0. The impacted element is an unknown function of the file orc8r/cloud/go/services/obsidian/access/operator.go of the component Obsidian REST. Executing a manipulation of the argument X-Magma-Client-Cert-Serial can lead to authentication bypass by spoofing. The attack can be launched remotely. The vendor was contacted early this disclosure but did not respond in any way.
**Risk verdict:** Treat this as a high-priority exposure review: the reported path is remotely reachable without authentication or user action, but KEV, SSVC and exploitation-likelihood data are not provided, so active exploitation cannot be confirmed.
**Why this matters:** An attacker who can spoof the client-certificate serial could gain unauthorised access to the management API. Potential outcomes include disclosure or alteration of operational data and service disruption; impact may be contained to the affected system, but its role in mobile-network operations can make even local compromise consequential.
**Most likely attack path:** A remote attacker sends crafted requests to an exposed Obsidian REST endpoint, with no apparent need for prior access or victim interaction. The stated scope is unchanged, so direct impact appears limited to the vulnerable system; access to other network components would depend on its permissions, integrations and reachable services.
**Who is most exposed:** Operators running Magma with Obsidian REST reachable from the internet, untrusted networks or broad internal segments are most exposed. Cloud and telecom deployments with centralised management interfaces warrant particular scrutiny.
Review API access logs for anomalous or repeated `X-Magma-Client-Cert-Serial` values.
Alert on unauthorised requests accepted by Obsidian REST and unexpected privileged API actions.
Check network flow records for external access to the management interface.
Mitigation and prioritisation
Establish whether a vendor fix or verified workaround is available; the supplied data does not confirm one.
Restrict endpoint access to trusted management hosts, using network ACLs or a VPN.
Review credentials, API activity and configuration changes for signs of misuse.
Test changes in a representative environment before rollout; monitor closely after deployment.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
