CVE-2026-92932 misp CVE debrief

Who should care

Defenders responsible for MISP sachertortephp library-based applications should assess their exposure and verify the Xml::build() method's input validation and the readFile option's usage. They should also monitor for potential SSRF attacks and implement compensating controls to prevent information disclosure.

Why it matters

The MISP sachertortephp library's Xml::build() method SSRF vulnerability allows an attacker to force the application to issue an outbound HTTPS request to an attacker-controlled or internal URL, enabling information disclosure. Defenders should verify the Xml::build() method's input validation and the readFile option's usage to prevent SSRF attacks.

• An attacker can force the application to issue an outbound HTTPS request to an attacker-controlled or internal URL, enabling information disclosure from internal services or external targets.
• The vulnerability requires that the code path in Xml::build() be reachable with attacker-controlled input and that the readFile option be set to false (or the caller expects it to be false).
• Defenders should verify the Xml::build() method's input validation and the readFile option's usage to prevent SSRF attacks.

Technical summary

The MISP sachertortephp library's Xml::build() method contains a logic error in the conditional that gates network-based XML fetching. This allows for Server-Side Request Forgery (SSRF) with an information-disclosure impact when the readFile option is set to false. The vulnerability occurs because the && operator has higher precedence than || in the conditional, causing an input string beginning with https:// to still satisfy the condition and trigger a network fetch via HttpSocket, even when the readFile option is set to false. An attacker who can influence the $input parameter passed to Xml::build() can therefore force the application to issue an outbound HTTPS request to an attacker-controlled or internal (

Defensive priority

Defenders should prioritize verifying the Xml::build() method's input validation and the readFile option's usage in their applications. They should also monitor for potential SSRF attacks and implement compensating controls to prevent information disclosure.

Recommended defensive actions

• Verify the Xml::build() method's input validation and the readFile option's usage in your application.
• Monitor for potential SSRF attacks and implement compensating controls to prevent information disclosure.
• Review the application's network configuration and restrict outbound requests to trusted URLs.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD vulnerability detail provide information about the vulnerability, but the scope of affected versions and remediation steps are not explicitly stated. Further verification is required to determine the impact and necessary mitigations.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.