Cyber Resilience

CVE-2026-42933

Published
23 July 2026
Modified
27 July 2026
CVSS Score v4 10.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0029 21th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2026-42933 is a critical-severity Confused Deputy (CWE-441) vulnerability. Its CVSS base score is 10.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Proxy (T1090); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SC-7 (Boundary Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1090 Proxy Command And Control
Adversaries may use a connection proxy to direct network traffic between systems or act as an intermediary for network communications to a command and control server to avoid direct connections to their infrastructure.
Why these techniques?

Direct proxy/intermediary weakness (CWE-441) enables attacker-controlled proxying to bypass network segmentation, mapping to Proxy technique.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-6993Shared CWE-441
CVE-2025-64123Shared CWE-441
CVE-2025-48579Shared CWE-441
CVE-2026-0107Shared CWE-441
CVE-2026-16158Shared CWE-441
CVE-2026-3160Shared CWE-441
CVE-2025-11393Shared CWE-441
CVE-2026-0013Shared CWE-441
CVE-2026-0098Shared CWE-441
CVE-2025-25061Shared CWE-441

Affected Assets

Pronetiqs IntraVUE
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-7 Boundary Protection
  • AC-4 Information Flow Enforcement
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.2.1
  • V3.5.1
  • V3.5.3
  • V3.5.8

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces network boundary protections and segmentation rules that block unauthorized proxies from bypassing OT network isolation.

prevent

Enforces approved information flow policies between network segments, preventing an unintended proxy from acting as an intermediary.

detect

Monitors network traffic and system activity to identify proxy-based attempts to circumvent OT segmentation controls.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-04 mostly match
prevents

Proper conveyance and verification of original identity assertions directly prevents loss of request source when forwarding.

PR.AA-05 partial match
prevents

Enforcing least-privilege authorizations on forwarded requests reduces confused-deputy abuse even if source identity is lost.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Access-control rules can limit which upstream identities may cause the product to act on their behalf, reducing confused-deputy risk.

prevents

Proper identity management ensures the original requester identity is preserved and validated before the product forwards requests.

degrades

Explicit access-rights assignment can restrict the product’s ability to act as an unintended proxy for external actors.

degrades

Privileged-access controls limit the rights the product may exercise on behalf of upstream callers, mitigating confused-deputy abuse.

degrades

Network-security controls can enforce source validation and prevent the product from blindly proxying traffic to external actors.

prevents

Secure-SDLC practices include design reviews that detect and eliminate confused-deputy proxy patterns before deployment.

References