Is CVE-2026-112179 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-112179 being exploited in the wild.

How severe is CVE-2026-112179?

Informational severity, published 19 October 2026.

Which products and versions are affected?

MISP Project MISP before 2.5.48.

Is there a fix for CVE-2026-112179?

Yes: fixed in 2.5.48. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-112179 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-112179?

Check whether you run MISP Project MISP 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.

CVE-2026-112179: MISP event synchronization information disclosure via tag filtering

CVE-2026-112179 · Severity: info · Published 2026-10-19

MISP is a threat intelligence sharing platform that distributes security events and reports between organizations. When pushing multiple threat reports to a remote MISP instance, the application failed to properly filter restricted tag information on all but the last report, causing sensitive metadata to be disclosed to the receiving server. Additionally, when the last report should have been withheld, a malformed null report was sent, causing synchronization failures.

Technologies: MISP Project MISP. Vendors: MISP Project.

Quick answers

Is CVE-2026-112179 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-112179 being exploited in the wild.
How severe is CVE-2026-112179?: Informational severity, published 19 October 2026.
Which products and versions are affected?: MISP Project MISP before 2.5.48.
Is there a fix for CVE-2026-112179?: Yes: fixed in 2.5.48. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112179 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-112179?: Check whether you run MISP Project MISP 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: 2.5.48

Technical details

The vulnerability stems from a logic error in event report preparation for synchronization: tag filtering for non-exportable and local tags was applied only once after iterating through all reports, rather than filtering each report individually. This allows restricted tag information to leak to remote instances on all reports except the last one, and can cause the remote instance to fail when the final report is properly withheld. The issue affects MISP instances configured to push events with multiple reports via server synchronization.

Affected products

MISP Project MISP before 2.5.48

Timeline

2026-10-19: disclosed

References

https://github.com/MISP/MISP/commit/0be4564a9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.