eigent auth bypass in Local Agent Control API chat_controller.py
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
A missing authentication flaw in the chat_controller.py file of the Local Agent Control API in eigent-ai's eigent software lets a remote attacker reach the affected functionality without logging in. Successful exploitation could have a low impact on confidentiality, integrity, and availability.
Written by a model
Original description
A vulnerability was detected in eigent-ai eigent up to 1.0.2. Affected by this vulnerability is an unknown functionality of the file backend/app/controller/chat_controller.py of the component Local Agent Control API. Performing a manipulation results in missing authentication. The attack may be initiated remotely. Upgrading to version 1.0.3 addresses this issue. The patch is named 59f43afcb1b0ba7b2de8c65d585124f196c4aa17. It is recommended to upgrade the affected component.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133983 (eigent-ai eigent Local Agent Control API chat_controller.py missing authentication), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133983 (entry last updated 2026-11-21):
Affected:
- eigent-ai eigent: versions 1.0.0, 1.0.1, 1.0.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133983 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133983 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/eigent-ai/eigent/pull/1842
- https://github.com/eigent-ai/eigent/commit/59f43afcb1b0ba7b2de8c65d585124f196c4aa17
- https://github.com/eigent-ai/eigent/releases/tag/v1.0.3
- https://vuldb.com/vuln/441574
- https://vuldb.com/vuln/441574/cti
- https://vuldb.com/cve/CVE-2026-133983
- https://vuldb.com/submit/1052008
- https://github.com/eigent-ai/eigent/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133983
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133983"}.Affected versions
- eigent-ai eigent1.0.0, 1.0.1, 1.0.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 10
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133983 |
| Record | NVD · CVE-2026-133983 |
| Other links 8 | |
| Advisory | VulDB · Advisory #441574 |
| Advisory | VulDB · Threat intelligence #441574 |
| Advisory | VulDB · CVE-2026-133983 record |
| Advisory | VulDB · Submission #1052008 |
| Patch | GitHub · eigent-ai/eigent · Pull request #1842 |
| Patch | GitHub · eigent-ai/eigent · Commit 59f43afc |
| Patch | GitHub · eigent-ai/eigent · Release v1.0.3 |
| Repository | GitHub · eigent-ai/eigent · Repository |
Questions about CVE-2026-133983
Is CVE-2026-133983 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133983?
eigent: versions 1.0.0, 1.0.1, 1.0.2.
Source: cve.now feed data
Related
- CVE-2025-689521-click Remote Code Execution (RCE) vulnerability in Eigent
- CVE-2026-22869Eigent Allows Arbitrary Code Execution via pull_request_target CI Workflow
- CVE-2026-80188BuddyBoss Addons <= 1.2.1 - Unauthenticated Account Takeover via Unverified Social Login Identity Tokens
- CVE-2026-96805Elecbrakes Missing Authentication for Critical Function
- CVE-2026-134287OpenRemote before 1.34.0 Authentication Bypass via X.509 MQTT Provisioning
- CVE-2026-134352Rclone 1.51.0 before 1.76.0 Authentication Bypass via serve sftp Auth-Proxy Cache
No corrections so far. Something wrong on this page? Report an error.