# CVE-2026-95674: MISP missing module availability validation in queryEnrichment

Source: https://junglewise.ai/threats/cve-2026-95674-in-misp-the-queryenrichment-method-in-eventscontroller-php  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-22. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-95674 · Severity: info · Published 2026-09-22

MISP, a threat intelligence platform, did not properly validate whether enrichment modules were enabled before processing requests. An authenticated user could request enrichment from disabled or non-existent modules, which would silently proceed with default settings rather than being rejected. This bypassed administrator controls over which analysis tools were available and could expose unintended functionality or data processing paths.

Technologies: [MISP Project MISP](https://junglewise.ai/threats/technologies/misp-project-misp). Vendors: [MISP Project](https://junglewise.ai/threats/vendors/misp-project).

## Quick answers

**Is CVE-2026-95674 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-95674 being exploited in the wild.

**How severe is CVE-2026-95674?** Informational severity, published 22 September 2026.

**Which products and versions are affected?** MISP Project MISP.

**Is there a fix for CVE-2026-95674?** A patch was published on 2026-09-22: Security hardening commit 7dfcc4d Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-95674 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-95674?** Check whether you run MISP Project MISP. 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.

## Technical details

The queryEnrichment method in EventsController.php accepted a module name parameter but failed to validate it against the list of enabled modules. If a module was not in the enabled list, the code continued processing with default parameters (format='simplified', no module-specific config) instead of rejecting the request. This allowed authenticated users to invoke disabled modules, circumventing intended access controls through insufficient input validation.

## Affected products

- MISP Project MISP

## Timeline

- 2026-09-22: disclosed
- 2026-09-22: patched: Security hardening commit 7dfcc4d

## References

- [https://github.com/MISP/MISP/commit/7dfcc4d32](https://github.com/MISP/MISP/commit/7dfcc4d32)

## Related threats

- [MISP module plugin settings flags not preserved](https://junglewise.ai/threats/cve-2026-112192-misp-contains-a-vulnerability-in-the-handling-of-module-plugin)
- [MISP server settings information disclosure](https://junglewise.ai/threats/cve-2026-112188-misp-contains-a-vulnerability-in-its-server-settings-lookup)
- [MISP reflected XSS in workflow module interface](https://junglewise.ai/threats/cve-2026-112184-misp-contains-a-reflected-cross-site-scripting-xss-vulnerability)
- [MISP data integrity flaw in event deletion logic](https://junglewise.ai/threats/cve-2026-112180-misp-contains-a-data-integrity-flaw-in-its-event-deletion-logic)
- [MISP event synchronization information disclosure via tag filtering](https://junglewise.ai/threats/cve-2026-112179-in-misp-the-event-synchronization-process-contained-a-logic)