Report · Zero Day InitiativeAbout CVE-2026-19908Published 5 Aug 2026

ZDI-26-524: (0Day) PAX Technology Q80 XCB Daemon Missing Authentication Vulnerability

Source Zero Day Initiative

Compare

Authoritative record:CVE-2026-19908· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PAX TechnologyQ80	Affected =2.6.33.6690R	Fixed in–

AI-suggested

The vendor disputes the impact on supported releases and has not provided a fix. The only effective mitigation is to restrict network access to the affected device, limiting interaction to trusted networks or isolating the device to prevent unauthorized access. Monitor vendor advisories for any future updates or support changes.

Description

This vulnerability allows network-adjacent attackers to disclose sensitive information and modify configuration on affected installations of PAX Technology Q80. Authentication is not required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 7.1. The following CVEs are assigned: CVE-2026-19908.

Impact

An attacker who is network-adjacent can exploit this vulnerability without any authentication to disclose sensitive information and modify configuration on the affected PAX Technology Q80 device. The vulnerability has a high severity rating (CVSS 7.1) due to the potential confidentiality impact and configuration modification. Additionally, it can be chained with other vulnerabilities to execute arbitrary code with root privileges, increasing the risk of full device compromise. No known exploits are reported in the wild at this time.

Summary

This vulnerability in the PAX Technology Q80's XCB daemon allows attackers on the same network to bypass authentication and access sensitive information or modify configuration settings. The root cause is the absence of authentication checks before granting access to daemon functionality. The Zero Day Initiative assigned a CVSS score of 7.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N). The vendor confirmed the affected firmware is end-of-life and no updates are available. Attempts to engage the vendor for remediation on supported releases were disputed, and the vendor requested an extension before public disclosure. The vulnerability can be leveraged with other flaws to achieve arbitrary code execution as root. The advisory recommends restricting network access to mitigate risk.

References

zerodayinitiative.com/advisories/ZDI-26-524/ (opens in a new tab)

Community reviews

Loading reviews…