Quick answers
- Is CVE-2026-107674 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107674 being exploited in the wild.
- How severe is CVE-2026-107674?
- Medium severity, with a CVSS score of 5.1, published 16 October 2026.
- Which products and versions are affected?
- IBM I 7.3, 7.4, 7.5, 7.6.
- Is there a fix for CVE-2026-107674?
- Yes: fixed in 7.3 (PTF SJ11843), 7.4 (PTF SJ11844), 7.5 (PTF SJ11845), 7.6 (PTF SJ11846). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107674 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-107674?
- Check whether you run IBM I 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: 7.3 (PTF SJ11843), 7.4 (PTF SJ11844), 7.5 (PTF SJ11845), 7.6 (PTF SJ11846)
Technical details
This vulnerability is an improper locking issue (CWE-667) in the Digital Certificate Manager that handles System TLS for secure network connections. It requires local access and high privileges to exploit; an attacker can trigger a denial of service condition that prevents DCM from functioning, potentially forcing applications to fall back to non-secure communications. Fixes are available via PTFs for all affected versions.
Affected products
- IBM i 7.3, 7.4, 7.5, 7.6
Timeline
- 2026-10-13: disclosed