Quick answers
- Is CVE-2026-113469 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113469 being exploited in the wild.
- How severe is CVE-2026-113469?
- High severity, with a CVSS score of 7.5, published 20 October 2026.
- Which products and versions are affected?
- Stormshield Network Security 4.3.0 to 4.3.44, 4.8.0 to 4.8.19, 5.0.0 to 5.0.9, 5.1.0 to 5.1.3.
- Is there a fix for CVE-2026-113469?
- Yes: fixed in SNS 5.1.4 EA, 5.0.10, 4.8.20 LTSB. Until then: Use only official Stormshield update servers or verified SMC mirror servers with HTTPS enabled. If using custom update servers, enable HTTPS and verify SHA-256 hashes of files match those from official Stormshield servers. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113469 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-113469?
- Check whether you run Stormshield Network Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: SNS 5.1.4 EA, 5.0.10, 4.8.20 LTSB
Use only official Stormshield update servers or verified SMC mirror servers with HTTPS enabled. If using custom update servers, enable HTTPS and verify SHA-256 hashes of files match those from official Stormshield servers.
Technical details
A logic error in the signature verification routine causes the SNS auto-update mechanism to accept unauthenticated dynamic data files during the update process. The vulnerability requires adjacent network proximity to exploit (AV:A) and has high attack complexity (AC:H), but results in high impact across confidentiality, integrity, and availability. An attacker could deliver malicious unsigned updates to compromise the device.
Affected products
- Stormshield Network Security 4.3.0 to 4.3.44, 4.8.0 to 4.8.19, 5.0.0 to 5.0.9, 5.1.0 to 5.1.3
Timeline
- 2026-10-16: disclosed: Initial advisory release
- 2026-08-03: other: Vulnerability discovered