Cyber & AI intelligence
Wasteland.
Briefs indexed2425
Issues26
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-85667 2026-09-04

CVE-2026-85667: Unauthenticated Webhook Message Injection in TeamWiseFlow xiaobei

"A critical missing-authentication flaw in TeamWiseFlow's xiaobei agent platform lets unauthenticated attackers inject arbitrary messages into the agent pipeline and pivot to server-side request forgery against internal…"

A critical missing-authentication flaw in TeamWiseFlow's xiaobei agent platform lets unauthenticated attackers inject arbitrary messages into the agent pipeline and pivot to server-side request forgery against internal services.

What Is It

xiaobei through version 5.5.2 fails to implement authentication or signature validation on its webhook endpoints. Any attacker who can reach the service over the network can publish messages through the /webhook_worktool handler without credentials, injecting arbitrary content directly into the agent processing pipeline.

The flaw carries a second stage: the handler fetches media URLs without validation, so an attacker-supplied URL can be used to make the server issue requests to internal services; classic server-side request forgery reachable from an entirely unauthenticated position.

VulnCheck, the disclosing party, classifies the root cause as CWE-306 (Missing Authentication for Critical Function).

Why It Matters

The CVSS v3.1 base score is 9.1 (CRITICAL), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. A CVSS v4.0 secondary score of 9.3 (CRITICAL) was also assigned.

Every exploitability dimension is worst-case: network attack vector, low attack complexity, no privileges, no user interaction. Confidentiality and integrity impacts are both HIGH, an attacker can both corrupt what the agent pipeline processes and use the SSRF primitive to reach data on internal networks. Availability is unaffected.

No CISA KEV entry was supplied for this CVE, so there is no confirmed evidence of active exploitation and no federal remediation deadline at this time.

What's Vulnerable

No CPE configuration data has been published in the NVD record yet.

Patch Status

The NVD record was published 2026-09-04 with a status of "Received"; it has not yet completed NVD analysis. No fixed version is identified in the supplied source material, and no vendor patch or required remediation action is specified. Tracking issue #440 in the upstream GitHub repository is referenced by the disclosure.

Sources