ag-ui-protocol ag-ui Multimodal Content utils.py urllib.request.urlopen server-side request forgery

CVE Details

• Protection status: Protected by Atomicorp rules · About protection statuses
• CVE: CVE-2026-92184
• Name: ag-ui-protocol ag-ui Multimodal Content utils.py urllib.request.urlopen server-side request forgery
• Severity: Medium
• CVSS: 5.3 (v4.0) (Medium)
• CVSS version: 4.0
• CVSS source: VulDB CNA
• CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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
  • Attack vector: Network
  • Attack complexity: Low
  • Attack requirements: None
  • Privileges required: Low
  • User interaction: None
  • Vulnerable-system confidentiality: Low
  • Vulnerable-system integrity: Low
  • Vulnerable-system availability: Low
  • Subsequent-system confidentiality: Negligible
  • Subsequent-system integrity: None
  • Subsequent-system availability: None
  • Safety: Not defined
• CWE: CWE-918
• Vendor: ag-ui-protocol
• Vulnerable product: ag-ui
• CVE published: 2026-09-16
• CVE last modified: 2026-09-16
• EPSS: 0.0028; 20.3th percentile as of 2026-09-16 (FIRST (opens in a new tab) )
• Latest Update: 2026-09-16
• Selected Rule IDs observed: 337109 , 337110 , 344360 , 398001 , 398008 , 398021 , 398022
• Matching rules: 7; rules with blocking actions: 5
• Would-block Rule IDs: 337109 , 337110 , 344360 , 398021 , 398022
• Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data

Vulnerability Description

A security flaw has been discovered in ag-ui-protocol ag-ui 0.3.0. Affected is the function urllib.request.urlopen of the file integrations/aws-strands/python/src/ag_ui_strands/utils.py of the component Multimodal Content. The manipulation of the argument Value results in server-side request forgery. The attack can be executed remotely. The patch is identified as bf0c34df34cbb4b1992bc37c9bfffe6dd54bb189. It is advisable to implement a patch to correct this issue.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (337109 , 337110 , 344360 , 398021 , 398022 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: ag-ui-protocol ag-ui version 0.3.0.
   • No specific CNA/vendor solution or workaround is included in the current CVE Record (opens in a new tab) . Review the vendor’s security advisories and supported-release guidance before making changes.

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• CVE authority reference: https://github.com/ag-ui-protocol/ag-ui/ (opens in a new tab)
• CVE authority reference: https://github.com/ag-ui-protocol/ag-ui/commit/bf0c34df34cbb4b1992bc37c9bfffe6dd54bb189 (opens in a new tab)
• CVE authority reference: https://github.com/ag-ui-protocol/ag-ui/issues/2432 (opens in a new tab)
• CVE authority reference: https://github.com/ag-ui-protocol/ag-ui/pull/2491 (opens in a new tab)
• CVE authority reference: https://vuldb.com/cve/CVE-2026-92184 (opens in a new tab)
• CVE authority reference: https://vuldb.com/submit/934100 (opens in a new tab)
• CVE authority reference: https://vuldb.com/vuln/404437 (opens in a new tab)
• CVE authority reference: https://vuldb.com/vuln/404437/cti (opens in a new tab)

Test or Research Source

• Source: Atomicorp AI Research Framework
• Tags: cve, derived, ssrf, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .