CVE-2026-7439

AgentFlow Local Web API Content-Type Validation Bypass

Published Apr 29, 2026 CVSS 4.0 · 4.8 Medium EPSS < 1% KEV · Not listed
Description
AgentFlow's local web API accepts non-JSON content types on POST /api/runs and POST /api/runs/validate endpoints without enforcing application/json validation, allowing attackers to bypass trust-boundary enforcement on sensitive operations. Attackers can exploit this content-type validation weakness through browser-driven or local cross-origin requests to abuse the localhost API and enable attack chains against the local control plane.

Analysis

AI-generated

Technical impact

AgentFlow’s local web API accepts POST requests to the /api/runs and /api/runs/validate endpoints without enforcing application/json validation. This content‑type validation weakness enables attackers to send arbitrary payloads that are accepted as valid, allowing them to bypass trust‑boundary enforcement on sensitive operations. The result is unauthorized access to the local control plane, potentially permitting attackers to trigger other privileged actions or embed further exploitation steps.

Affected Systems

The vulnerability affects the Berabuddies AgentFlow product. No specific version information is provided, so users should check whether their installed instance contains the affected API endpoints.

Risk and Exploitability

The CVSS score of 4.8 indicates moderate severity. EPSS data is not available and the vulnerability is not listed in CISA’s KEV catalog. The likely exploitation path is local: an attacker who can run scripts in the user’s browser or has other local access can craft requests that override the expected JSON content type and exploit the control‑plane API. While the risk is moderate, it can serve as a stepping stone in a larger attack chain against the local system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest patch or upgrade AgentFlow to a version that implements strict content‑type validation for the /api/runs and /api/runs/validate endpoints.
  • Configure the local web server or application gateway to reject any POST payload that does not specify application/json, effectively denying non‑JSON requests to the API.
  • If the affected endpoints are not required in your deployment, remove or block them and restrict local API access to trusted users or processes.

Generated by OpenCVE AI on April 29, 2026 at 21:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Berabuddies
Berabuddies agentflow
Vendors & Products Berabuddies
Berabuddies agentflow
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description AgentFlow's local web API accepts non-JSON content types on POST /api/runs and POST /api/runs/validate endpoints without enforcing application/json validation, allowing attackers to bypass trust-boundary enforcement on sensitive operations. Attackers can exploit this content-type validation weakness through browser-driven or local cross-origin requests to abuse the localhost API and enable attack chains against the local control plane.
Title AgentFlow Local Web API Content-Type Validation Bypass
Weaknesses CWE-346
References
Metrics cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 4.8, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 8, 2026, 2:08 PM
Reserved
Apr 29, 2026, 3:46 PM
Status
Deferred
Published
Apr 29, 2026, 7:16 PM
Modified
Oct 26, 2026, 8:10 PM