Security readout for executives and security teams
Plain-English summary
An internet-reachable xiaobei webhook may accept messages from anyone because it lacks authentication or signature checks. Crafted messages can enter the agent pipeline, and supplied media URLs may cause the server to contact internal services. This creates serious risks to sensitive data and system integrity.
Executive priority
Treat internet-accessible deployments as an immediate remediation priority because compromise could affect confidentiality and integrity without credentials or user action. First reduce webhook and outbound-network exposure, then apply vendor-supported remediation when confirmed. Investigate suspicious historical activity.
Technical view
CVE-2026-85667 affects the /webhook_worktool handler described in xiaobei through 5.5.2. Missing webhook authentication or signature validation permits unauthenticated message injection. Unvalidated server-side media retrieval also creates an SSRF path toward internal services. The supplied CVSS 4.0 score is 9.3.
Likely exposure
Risk is highest where the xiaobei webhook is reachable from untrusted networks and the server can access sensitive internal services. The bundle describes versions through 5.5.2, but its structured affected-version data is inconsistent, so inventories require careful verification.
Exploitation context
The attack requires network access but no privileges or user interaction, according to the supplied vector. The source bundle does not cite observed exploitation, and its KEV indicator is false. Exploit prevalence is therefore unknown.
Researcher notes
The sources describe message injection plus SSRF and identify code at the v5.5.2 tag. However, the bundle's narrative says “through 5.5.2,” while its structured affected entry lists version “0” with default status unaffected. No fixed version, vendor patch, proof of exploitation, or KEV listing is provided.
Mitigation direction
- Identify xiaobei deployments and determine whether /webhook_worktool is reachable from untrusted networks.
- Restrict webhook access to trusted senders or networks until authoritative vendor remediation is available.
- Limit the xiaobei server's outbound access to internal services and sensitive metadata endpoints.
- Check TeamWiseFlow guidance for a fixed release or supported authentication mechanism.
- Preserve relevant webhook, agent, proxy, and outbound-request logs for investigation.
Validation and detection
- Confirm deployed xiaobei versions using package, image, or release metadata.
- Review reverse-proxy and firewall rules governing access to /webhook_worktool.
- Verify whether webhook requests receive cryptographic signature or equivalent sender validation.
- Inspect logs for unexpected webhook messages and unusual server-originated requests to internal addresses.
- Confirm outbound network controls prevent unnecessary access from xiaobei to sensitive internal services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-85667 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Issue #440CVE reference, VulnCheck · issue-tracking
- https://github.com/TeamWiseFlow/xiaobeiCVE reference, VulnCheck · product
- https://github.com/TeamWiseFlow/xiaobei/blob/v5.5.2/awada/awada-server/src/routes/webhook-worktool.tsCVE reference, VulnCheck · technical-description
- VulnCheck Advisory: xiaobei through 5.5.2 Unauthenticated Webhook Message InjectionCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.