What is the CVSS score of CVE-2026-36719?

CVE-2026-36719 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of AgentChat are affected by CVE-2026-36719?

AgentChat v2.3.0 contains an unauthenticated vulnerability exposing all users' account information and password hashes to remote attackers without authentication required.

How to fix or mitigate CVE-2026-36719?

Within 24 hours: Immediately restrict network access to the /api/v1/user/info endpoint via firewall or WAF rules to prevent sequential ID enumeration, and enable logging to detect exploitation attempts. Within 7 days: Conduct forensic audit of access logs to confirm whether prior unauthorized data extraction occurred, reset all user passwords, and notify users of the exposure incident. Within 30 days: Execute complete migration away from AgentChat v2.3.0 to an alternative product or patched version, as no vendor patch is currently available for this version.

AgentChat CVE-2026-36719

HIGH

Information Exposure (CWE-200)

2026-06-09 mitre

Information Disclosure N A

7.5

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

vuln.today AI

7.5 HIGH

Unauthenticated network endpoint with no user interaction (PR:N/UI:N/AC:L); leaking password hashes yields high confidentiality impact with no integrity or availability effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 23, 2026 - 17:13 vuln.today

CVE Published

Jun 09, 2026 - 00:00 cve.org

HIGH 7.5

CVE Published

Jun 09, 2026 - 00:00 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

An information disclosure vulnerability in the /api/v1/user/info endpoint of AgentChat v2.3.0 allows unauthenticated attackers to obtain sensitive information, including SHA256 password hashes, via enumerating user IDs.

AnalysisAI

Sensitive information disclosure in AgentChat v2.3.0 lets unauthenticated remote attackers read other users' account data - including SHA256 password hashes - by enumerating sequential user IDs against the /api/v1/user/info endpoint. Because no authentication is required (PR:N) and the endpoint is directly reachable over the network, an attacker can harvest the full user table and then crack the recovered hashes offline. Publicly available exploit code exists (referenced POC and SSVC 'poc' status), though EPSS remains very low (0.02%) and the flaw is not listed in CISA KEV.

Technical ContextAI

AgentChat exposes a REST API whose /api/v1/user/info endpoint returns per-user profile data keyed by a user identifier. The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): the endpoint applies no authorization check tying the requester to the requested user record, and it returns security-sensitive fields - notably the stored SHA256 password hash - in its response body. Because user IDs appear to be predictable and enumerable, an attacker can iterate the ID space (an IDOR/BOLA-style access pattern) to dump every account. SHA256 without documented salting or key-stretching (bcrypt/scrypt/argon2) is fast to brute-force, compounding the impact once hashes are exposed. The provided CPE string (cpe:2.3:a:n/a:n/a:*) is a placeholder and does not authoritatively identify the vendor/product beyond the description.

RemediationAI

No vendor-released patch identified at time of analysis, and no fixed version is provided in the source data. The primary compensating control is to enforce authentication and per-object authorization on /api/v1/user/info so a caller can only retrieve its own record and requests for arbitrary user IDs are rejected (trade-off: minimal, restores intended behavior). Until a fix ships, restrict network exposure of the API by placing it behind a VPN or IP allowlist or blocking external access to the endpoint at a reverse proxy/WAF, and add rate-limiting on the endpoint to slow ID enumeration (trade-off: WAF rules may need tuning to avoid breaking legitimate clients). Critically, treat all stored SHA256 hashes as compromised: force a password reset for all users and migrate password storage to a salted, memory-hard algorithm such as bcrypt, scrypt, or argon2. Review the researcher writeup at https://github.com/CC-T-454455/Vulnerabilities/tree/master/agent-chat/vulnerability-3 for exploit specifics.