CVE-2026-36719
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe /api/v1/user/info endpoint in AgentChat v2.3.0 exposes sensitive user data including SHA256 password hashes to unauthenticated attackers. By systematically enumerating user IDs, attackers can harvest credentials for all users in the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify AgentChat installation and versionLocate the AgentChat application on your system and determine the installed version. Common methods include checking the application binary, startup logs, or package manager output. Compare your version to v2.3.0.Affected if The installed version is AgentChat v2.3.0 exactly, or falls within the v2.3.0 release line.
-
Confirm the /api/v1/user/info endpoint existsMake an HTTP GET request to http(s)://<your-server>:<port>/api/v1/user/info using a tool like curl. Observe whether the endpoint responds (returns 200, 401, or other status).Affected if The endpoint returns any HTTP response (including 200 OK or 400/401 errors), indicating the endpoint is exposed.
-
Test endpoint authentication requirementSend a request to /api/v1/user/info WITHOUT any authentication tokens, headers, or cookies. Then send the same request WITH valid credentials if available. Compare the responses.Affected if The endpoint returns user data or any sensitive information WITHOUT requiring authentication credentials.
-
Inspect response for password hash exposureExamine the JSON or other response body from the /api/v1/user/info endpoint. Look for fields containing hash values, particularly SHA256 hashes, or fields named password, hash, pwd, or similar.Affected if The response contains SHA256 password hashes or any password hash data in the API response body.
You are affected if AgentChat v2.3.0 is running and the /api/v1/user/info endpoint is accessible without authentication credentials and returns password hash data in the response.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement authentication and role-based authorization on the /api/v1/user/info endpoint, ensure password hashes are never returned in API responses, and add rate limiting to prevent enumeration attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data