CVE-2026-120237 ag-ui-protocol CVE debrief

Who should care

Defenders and security teams should assess exposure and prioritize verification of affected versions. They should also monitor for exploitation attempts and resource consumption issues. Affected product deployments should be confirmed in managed environments and assigned an owner for follow-up. Official advisories or CVE records should be reviewed to validate affected scope, severity, and vendor guidance.

Why it matters

A flaw in ag-ui-protocol ag-ui up to 0.0.58 can cause resource consumption through the isInterruptExpired function. Remote exploitation is possible. Defenders should assess exposure, prioritize verification of affected versions, and monitor for exploitation attempts.

• Verify affected versions and remediation steps
• Monitor for exploitation attempts and resource consumption issues
• Assess exposure and prioritize patching

Technical summary

The isInterruptExpired function in ag-ui-protocol ag-ui up to 0.0.58 can cause resource consumption. Remote exploitation of the attack is possible. This issue affects the component Interrupt expiry. The exploit has been published and may be used. Defenders should assess exposure, prioritize verification of affected versions, and monitor for exploitation attempts and resource consumption issues. The affected product context requires verification from official sources to ensure accurate defensive impact assessment. Affected operator, platform, vulnerability-management, and security-team impact should be considered.

Defensive priority

Defenders should assess exposure, prioritize verification of affected versions, and monitor for exploitation attempts.

Recommended defensive actions

• Assess exposure by checking if the ag-ui-protocol ag-ui version is up to 0.0.58
• Verify the affected versions and remediation steps from official sources
• Monitor for exploitation attempts and resource consumption issues
• 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
• Review compensating controls for exposed systems while remediation is scheduled and verified

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, the affected versions and remediation steps require verification from the official sources. The exploit has been published and may be used. Affected product deployments should be confirmed in managed environments and assigned an owner for follow-up. Official advisories or CVE records should be reviewed to validate affected scope, severity, and vendor guidance.

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.