CVE-2026-112188
MISP Server Settings Lookup Exposes Sensitive Configuration Data via Branch Name Resolution
02 Description
MISP Server Settings Lookup Exposes Sensitive Configuration Data via Branch Name Resolution
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.27% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 19.1% of scored records. A rank, not a probability.
- NVD base score
- 7.1 (CVSS v4.0), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- NVD analysis status
- Deferred. NVD last modified this record on 2026-10-28.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-19 09:22Z10 DAYS AGO
- Last updated
- 2026-10-28 20:05Z16 HR AGO
- Reserved
- 2026-10-19
- Assigning CNA
- CIRCL
- Record state
- PUBLISHED
- Severity
- High (CVSS 7.1)
- CNA CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Weaknesses
- Data version
- 5.2
- Document digest
- 629699c38d644231077c51b261e8ba31b92abb02d8d61e534bbd83a78adefbb2
05 Affected products
06 References
- github.comSecurity patchhttps://github.com/MISP/MISP/commit/30b849102
07 Remediation
The settings lookup function now validates that the resolved node is a leaf setting (has a 'level' property and is not an array representing a branch). If the resolved node is a branch or otherwise does not represent a single setting, the function returns false, indicating an invalid setting. This prevents the redaction check from being bypassed and stops the endpoints from returning entire configuration branches containing sensitive values.