---
id: "CVE-2026-116372"
kind: "vulnerability"
aliases: ["CVE-2026-116372"]
title: "MISP mispguard: non-200 2xx feed responses skip filtering rules"
severity: "high"
cvss: 7.7
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["misp", "mispguard", "package", "self-hosted", "threat-intel"]
not_affected_if: ["no-external-feeds", "no-mispguard"]
published_at: "2026-10-26T09:16:35+00:00"
first_seen_at: "2026-10-26T09:29:15+00:00"
updated_at: "2026-10-26T09:30:49+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116372", "first_seen_at": "2026-10-26T09:29:15+00:00"}]
---

# MISP mispguard: non-200 2xx feed responses skip filtering rules

mispguard is a proxy that filters MISP feed responses before MISP ingests them. Responses with 2xx codes other than 200, such as 203 or 206, bypassed the filter, so a malicious or compromised feed host can push unfiltered content into MISP.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed mispguard version in the MISP deployment, as the sources do not name the fixed release.
- Review `src/mispguard.py` and look for `process_feed_response` handling only non-200 status codes.
- List configured MISP feeds and note any fed by hosts outside your control.

## Fix

- Upgrade mispguard to a release that filters all 2xx responses; the fixed version is unknown from the sources.
- Until patched, restrict MISP feeds to trusted hosts.

## Timeline

- 2026-10-26T09:29:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-116372

## From the sources

MISP mispguard is a security filtering proxy that inspects and blocks MISP feed responses based on configured rules. The process_feed_response method in src/mispguard.py was responsible for evaluating feed responses before they reached the MISP instance. The original logic only explicitly handled the case where the HTTP status code was not 200 by passing the response through without filtering, on the assumption that non-200 responses would not carry ingestible event data. However, HTTP 2xx status codes other than 200 (such as 201 Created, 203 Non-Authoritative Information, and 206 Partial Content) were also passed through unfiltered. Because MISP may still ingest content from these responses, a malicious or compromised feed host could return a 203 or 206 status code with arbitrary content, effectively bypassing all of mispguard's filtering rules. This allowed unfiltered or malicious feed data to be ingested into the MISP instance, undermining the security controls that mispguard is designed to enforce. The vulnerability requires the attacker to control or compromise a feed endpoint configured in the MISP instance. No authentication or user interaction is required beyond the feed polling mechanism already in place.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_