CVE-2026-40434
Anviz Crosschex Standard
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2026-40434 is a high-severity Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Anviz Crosschex Standard. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique ARP Cache Poisoning (T1557.002); ranked at the 14th 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-17 (Remote Access) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-40434 is a vulnerability in Anviz CrossChex Standard, where the client/server channel lacks source verification, as defined by CWE-940 (Improper Verification of Source of a Communication Channel). This flaw enables TCP packet injection by an attacker on the same network, allowing them to alter or disrupt application traffic. The vulnerability received a CVSS v3.1 base score of 8.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H), highlighting high impacts on integrity and availability with no confidentiality impact.
An adjacent network attacker can exploit this issue with low complexity, no required privileges, and no user interaction. Exploitation involves injecting malicious TCP packets into the client/server communication, enabling the attacker to modify traffic content or cause disruptions such as denial of service.
Advisories including CISA ICSA-26-106-03 (https://www.cisa.gov/news-events/ics-advisories/icsa-26-106-03) and the associated CSAF file (https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-106-03.json) provide further details. Anviz support is available at https://www.anviz.com/contact-us.html.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23533
Vulnerability Data
Anviz CrossChex Standard lacks source verification in the client/server channel, enabling TCP packet injection by an attacker on the same network to alter or disrupt application traffic.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.3V10.6.2V15.2.4
Mitigating Controls (NIST 800-53 r5) AI
IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.
AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.
SC-23 protects session authenticity, ensuring the source of an established communication channel is verified and cannot be spoofed.
SC-7 enforces monitoring and control at external and key internal interfaces, preventing channels from unverified sources via boundary rules.
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.
Authentication of users/services/hardware directly enforces source verification for communication channels.
Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.
Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.
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.
Secure authentication mechanisms verify the identity and origin of communication channel initiators.
Network security controls enforce source verification and channel authentication for incoming communications.
Security of network services includes validating the origin of service requests and connections.
Network segregation limits exposure but does not directly verify source of individual channels.
Cryptography can support channel authentication but does not inherently verify source without proper implementation.
Application security requirements may specify origin checks but do not mandate them.