How severe is CVE-2026-50101?

CVE-2026-50101 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-50101 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-50101?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-50101 have an EU (EUVD) identifier?

Yes. CVE-2026-50101 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-36526.

When was CVE-2026-50101 published?

CVE-2026-50101 was published on 2026-06-12 and last updated on 2026-06-17.

CVE-2026-50101

CVE-2026-50101 is a high-severity vulnerability with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-262.

Key facts

Severity: High (CVSS 3.x base score 8.1)
CVSS v4: 9.2
EPSS exploit prediction: 0% (20th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-36526
Weakness: CWE-262
Published: 2026-06-12
Last modified: 2026-06-17

Description

Naxclow devices use a server-side, per-device relay credential that never rotates and is re-issued to the device on each boot. Because this credential remains valid indefinitely and cannot be reset or revoked by the legitimate owner, any party that obtains it through any exposure path can maintain persistent access to the device’s relay channel. This enables long-term impersonation or interception, even after factory resets or re-onboarding.

Frequently asked questions

What is CVE-2026-50101?: Naxclow devices use a server-side, per-device relay credential that never rotates and is re-issued to the device on each boot. Because this credential remains valid indefinitely and cannot be reset or revoked by the legitimate owner, any party that obtains it through any exposure path can maintain persistent access to the device’s relay channel. This enables long-term impersonation or interception, even after factory resets or re-onboarding.
How severe is CVE-2026-50101?: CVE-2026-50101 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-50101 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-50101?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-50101 have an EU (EUVD) identifier?: Yes. CVE-2026-50101 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-36526.
When was CVE-2026-50101 published?: CVE-2026-50101 was published on 2026-06-12 and last updated on 2026-06-17.

References

Other CWE-262 vulnerabilities

CVE-2025-60010 — Medium (CVSS 5.4): A password aging vulnerability in the RADIUS client of Juniper Networks Junos OS and Junos OS Evolved allows an…
CVE-2023-2022 — Medium (CVSS 4.3): An issue has been discovered in GitLab CE/EE affecting all versions starting before 16.0.8, all versions starting from…
CVE-2025-58435 — Medium (CVSS 4.1): Open OnDemand is an open-source HPC portal. Prior to versions 3.1.15 and 4.0.7, noVNC interactive applications did not…
CVE-2023-1555 — Low (CVSS 2.7): An issue has been discovered in GitLab affecting all versions starting from 15.2 before 16.1.5, all versions starting…

Browse all CWE-262 vulnerabilities →