CVE-2026-86237 openagents-org CVE debrief

Who should care

Defenders responsible for openagents-org openagents deployments should assess exposure and prioritize verification and compensating controls. Openagents-org openagents users should verify the presence of vulnerable code in their inventory, assess exposure, and apply compensating controls to mitigate potential server-side request forgery attacks.

Why it matters

Defenders should prioritize verifying the presence of the vulnerable code in their inventory, assessing exposure, and applying compensating controls to mitigate potential server-side request forgery attacks.

• Verify the presence of vulnerable code in inventory
• Assess exposure to server-side request forgery attacks
• Apply compensating controls to mitigate potential exploitation

Technical summary

The vulnerability is located in the test_default_model function of the http.py file in the openagents-sdk. An attacker can manipulate the base_url argument to perform a server-side request forgery attack. The vulnerability was found in openagents-org openagents up to 0.8.19/0.9.3.post20. Impacted is the function test_default_model of the file sdk/src/openagents/sdk/transports/http.py. The attack may be initiated remotely and has been made public. Endpoint and both sinks unchanged since filing; only the file moved (e277dd1a).

Defensive priority

Defenders should prioritize verifying the presence of the vulnerable code in their inventory, assessing exposure, and applying compensating controls.

Recommended defensive actions

• Verify the presence of the vulnerable code in inventory
• Assess exposure and apply compensating controls
• Monitor for potential exploitation attempts
• 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
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the corpus lacks information on actual exploitation, victims, or business impact. Openagents-org openagents deployments should verify the presence of vulnerable code in their inventory, assess exposure, and apply compensating controls to mitigate potential server-side request forgery attacks. Defenders should prioritize verifying the presence of the vulnerable code in their inventory, assessing exposure, and applying compensating controls. The attack may be initiated remotely and has been made public.

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.