Read the docs
TI-2026-06341 Aliases CVE-2026-7223GHSA-r2jq-4h3x-rfj6

BigSweetPotatoStudio HyperChat AI Proxy Middleware aiProxyMiddleware.mts fetch server-side request forgery

Priority HIGH 70CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
Low · Low · Low
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub.

Summary

A vulnerability was identified in BigSweetPotatoStudio HyperChat up to 2.0.0-alpha.63. Affected by this issue is the function fetch of the file packages/core/src/http/aiProxyMiddleware.mts of the component AI Proxy Middleware. Such manipulation of the argument baseurl leads to server-side request forgery. The attack can be launched remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00278 20th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
BigSweetPotatoStudioHyperChat2.0.0-alpha.0; 2.0.0-alpha.1; 2.0.0-alpha.2; 2.0.0-alpha.3; 2.0.0-alpha.4; 2.0.0-alpha.5; 2.0.0-alpha.6; 2.0.0-alpha.7; 2.0.0-alpha.8; 2.0.0-alpha.9; 2.0.0-alpha.10; 2.0.0-alpha.11; 2.0.0-alpha.12; 2.0.0-alpha.13; 2.0.0-alpha.14; 2.0.0-alpha.15; 2.0.0-alpha.16; 2.0.0-alpha.17; 2.0.0-alpha.18; 2.0.0-alpha.19; 2.0.0-alpha.20; 2.0.0-alpha.21; 2.0.0-alpha.22; 2.0.0-alpha.23; 2.0.0-alpha.24; 2.0.0-alpha.25; 2.0.0-alpha.26; 2.0.0-alpha.27; 2.0.0-alpha.28; 2.0.0-alpha.29; 2.0.0-alpha.30; 2.0.0-alpha.31; 2.0.0-alpha.32; 2.0.0-alpha.33; 2.0.0-alpha.34; 2.0.0-alpha.35; 2.0.0-alpha.36; 2.0.0-alpha.37; 2.0.0-alpha.38; 2.0.0-alpha.39; 2.0.0-alpha.40; 2.0.0-alpha.41; 2.0.0-alpha.42; 2.0.0-alpha.43; 2.0.0-alpha.44; 2.0.0-alpha.45; 2.0.0-alpha.46; 2.0.0-alpha.47; 2.0.0-alpha.48; 2.0.0-alpha.49; 2.0.0-alpha.50; 2.0.0-alpha.51; 2.0.0-alpha.52; 2.0.0-alpha.53; 2.0.0-alpha.54; 2.0.0-alpha.55; 2.0.0-alpha.56; 2.0.0-alpha.57; 2.0.0-alpha.58; 2.0.0-alpha.59; 2.0.0-alpha.60; 2.0.0-alpha.61; 2.0.0-alpha.62; 2.0.0-alpha.63—No fix listedCNA
—@dadigua/hyperchat (npm)up to 2.0.0-alpha.63—No fix listedGHSA-r2jq-4h3x-rfj6
  • HyperChat VendorBigSweetPotatoStudio Affected 2.0.0-alpha.0; 2.0.0-alpha.1; 2.0.0-alpha.2; 2.0.0-alpha.3; 2.0.0-alpha.4; 2.0.0-alpha.5; 2.0.0-alpha.6; 2.0.0-alpha.7; 2.0.0-alpha.8; 2.0.0-alpha.9; 2.0.0-alpha.10; 2.0.0-alpha.11; 2.0.0-alpha.12; 2.0.0-alpha.13; 2.0.0-alpha.14; 2.0.0-alpha.15; 2.0.0-alpha.16; 2.0.0-alpha.17; 2.0.0-alpha.18; 2.0.0-alpha.19; 2.0.0-alpha.20; 2.0.0-alpha.21; 2.0.0-alpha.22; 2.0.0-alpha.23; 2.0.0-alpha.24; 2.0.0-alpha.25; 2.0.0-alpha.26; 2.0.0-alpha.27; 2.0.0-alpha.28; 2.0.0-alpha.29; 2.0.0-alpha.30; 2.0.0-alpha.31; 2.0.0-alpha.32; 2.0.0-alpha.33; 2.0.0-alpha.34; 2.0.0-alpha.35; 2.0.0-alpha.36; 2.0.0-alpha.37; 2.0.0-alpha.38; 2.0.0-alpha.39; 2.0.0-alpha.40; 2.0.0-alpha.41; 2.0.0-alpha.42; 2.0.0-alpha.43; 2.0.0-alpha.44; 2.0.0-alpha.45; 2.0.0-alpha.46; 2.0.0-alpha.47; 2.0.0-alpha.48; 2.0.0-alpha.49; 2.0.0-alpha.50; 2.0.0-alpha.51; 2.0.0-alpha.52; 2.0.0-alpha.53; 2.0.0-alpha.54; 2.0.0-alpha.55; 2.0.0-alpha.56; 2.0.0-alpha.57; 2.0.0-alpha.58; 2.0.0-alpha.59; 2.0.0-alpha.60; 2.0.0-alpha.61; 2.0.0-alpha.62; 2.0.0-alpha.63 Fixed in — No fix listed CNA
  • @dadigua/hyperchat (npm) Vendor— Affected up to 2.0.0-alpha.63 Fixed in — No fix listed GHSA-r2jq-4h3x-rfj6

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-7223
  2. 2026-10-03 Alias added: GHSA-r2jq-4h3x-rfj6

References

Sources