Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.1

How to Fix CVE-2026-7399: PDKS (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-7399 is a sibling vulnerability in the same vendor advisory as CVE-2026-7382. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 8.1 - High
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-7382
Fixed inSame patched build as CVE-2026-7382 (See vendor advisory)
Type (CWE)CWE-639: CWE-639 Authorization bypass through User-Controlled key

What's different about CVE-2026-7399?

Authorization bypass through User-Controlled key vulnerability in MeWare Software Development Inc. PDKS allows Privilege Abuse.

This issue affects PDKS: from V16.20200313 before VMYR_3.5.2025117.

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-7399

Apply the patched build per the primary write-up: How to Fix CVE-2026-7382.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-7399 fixed by the same patch as CVE-2026-7382?

Yes. CVE-2026-7399 ships in the same vendor advisory as CVE-2026-7382. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-7399?

The CVSS base score is 8.1 (High).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the PDKS bundle. Full procedure at CVE-2026-7382.*