Skip to main content
Mallory
High

Improper authorization in Naxclow relay registration credential API

IdentifiersCVE-2026-50108CWE-863

CVE-2026-50108 is an improper authorization flaw in the Naxclow platform API endpoint that returns device relay registration details. According to the provided content, the endpoint exposes a persistent relay credential without verifying that the requester is the legitimate device or the device owner. As a result, an actor who can submit a platform-valid signed request can query relay registration details for arbitrary devices and recover the credentials used to register those devices on the relay service. Because the credential is described as persistent, compromise is not limited to a single session and can enable ongoing unauthorized access to relay-mediated communications.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthorized actor to retrieve relay registration credentials for arbitrary Naxclow devices and then register on the relay service as those devices. This enables impersonation of targeted devices and can lead to interception of device communications, unauthorized access to relay-mediated traffic, and disruption of communications by taking over or conflicting with the legitimate device’s relay registration.

Mitigation

If you can’t patch tonight, do this now.

No official vendor patch is available in the provided content. Recommended mitigations from the source material include isolating affected Naxclow devices on a separate network or VLAN, blocking internet access for affected devices wherever possible, reviewing the full CISA ICS advisory for technical details, and considering retirement or replacement of affected cameras and doorbells until the vendor provides a fix.

Remediation

Patch, then assume compromise.

Modify the affected Naxclow platform API so that requests for device relay registration details are authorized against the authenticated principal and the specific target device. The service should verify that the requester is the legitimate device itself or an explicitly authorized owner/administrator for that device before returning any relay registration material. Persistent relay credentials should be rotated for affected devices, especially if exposure is suspected. If feasible, replace long-lived relay registration secrets with short-lived, scoped, per-request or per-session credentials and ensure device identity binding on the relay side to prevent reuse for impersonation.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NaxclowPlatform Apiapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.