In this article
MISP 2.5.52 bundles more than fifty security fixes
MISP 2.5.52 is a major security release with more than fifty security fixes and hardening changes, and the project strongly recommends upgrading as soon as possible.
The fixes cover access control across the API and UI, synchronisation and feeds, protected event signing, authentication, exports, and several cross-site scripting issues in the user interface. Further fixes in workflows, Redis, correlation, STIX and other areas are listed as correctness fixes, including a Zeek export that previously ignored its tag filters.
The project credits an in-depth ENISA security review for most of the fixes, plus reports from Jeroen Pinoy and from Francois-Xavier Stellamans of the NATO Cyber Security Centre.
Affected versions and exploitation status are not stated
The release page does not say which earlier versions are affected by the security flaws. It also does not say whether any of the security fixes are known to be exploited. It gives no CVE identifiers or CVSS scores for the fixes.
Update to MISP 2.5.52 and review changed settings
After upgrading, apply the database updates by logging in as an admin or by running the runUpdates command as the web user. Restart PHP-FPM and the background workers when prompted. The three migrations repair Redis values stored PHP-serialised, remove auth keys and settings left by deleted users, and clean up stale sharing group references on collections. Commands and setting names here come from the documentation listed under Sources; check them against your own installation before running.
Check these changes before you upgrade, because some can break a working setup.
- Python: MISP's Python environment now needs 3.11 or newer, and PyMISP 3.0.0 and the matching misp-stix no longer install on Python 3.10.
- Ubuntu 22.04: it ships Python 3.10 by default, so install a newer Python, rebuild the virtual environment and point
MISP.python_binat it. - Proxies: with
MISP.log_client_ip_headerset, the client address now comes from the right-most end of the header, so list every proxy in the newMISP.trusted_proxiessetting if you run more than one. - Password resets: reset e-mails go out only when
MISP.baseurlorMISP.external_baseurlis configured, since the link is no longer built from the Host header. - CertAuth: it accepts only client certificates the web server has verified (
SSL_CLIENT_VERIFY=SUCCESS). - Compressed requests: only authenticated users can send them, only as gzip, and the new
Security.max_decompressed_sizecaps decompressed size, defaulting to the PHP memory limit. - Large events: set
Security.max_decompressed_sizehigh enough for the JSON of your largest events. - External authentication: with LDAP or Shibboleth configured, only site admins can change a user's login e-mail.
The release also removes event recovery from the logs (events/restoreDeletedEvents, events/recoverEvent and its CLI command) and the STIX sightings upload endpoint POST /sightings/add/stix. The legacy STIX 1 importer is gone too, so STIX 1 imports now go through misp-stix. Deleting a user now also deletes their auth keys and user settings. OIDC refresh tokens are stored encrypted when Security.encryption_key is set, and existing plaintext tokens keep working.
New features arrive alongside the fixes
MISP 2.5 instances can now sync with MISP 3.x instances. misp-modules gathering modules can serve as a feed source through the existing feed importer. CIDR correlation is skipped for very broad prefixes: IPv4 shorter than /8 and IPv6 shorter than /16. The Overmind interface gains a Timeline tab, new event-view cards, a zoom and filter mode for the correlation graph, and bulk deletes on index pages.
| Product | Affected | Fixed |
|---|---|---|
| MISP | Earlier versions (range not stated) | 2.5.52 |
Sources
Image: “Padlocks Locked” by Alexey Topolyanskiy, CC0 1.0, via stocksnap (Openverse)
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].


Discussion