# CVE-2025-41023: Authentication bypass in AutoGPT de Thesamur

> Attackers can bypass authentication in Thesamur's AutoGPT to access all features without credentials, requiring immediate attention from users.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-wmwp-mm98-6v2w

## What is CVE-2025-41023?

CVE-2025-41023 is a medium-severity authentication bypass vulnerability in Thesamur AutoGPT, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability has been found in Thesamur's AutoGPT. This vulnerability allows an attacker to bypass authentication mechanisms. Once inside the web application, the attacker can use any of its features regardless of the authorisation method used.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-41023?


## How do I fix CVE-2025-41023?

No fix has been published for CVE-2025-41023 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-41023 being exploited?

There is no known exploitation of CVE-2025-41023 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41023 and fix it if it is affected.

What it is: CVE-2025-41023 is a medium-severity authentication bypass vulnerability in Thesamur AutoGPT, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41023 in the wild and no public exploit code.

Affected product: Thesamur AutoGPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-41023/ (Markdown: https://insights.sbomify.com/CVE-2025-41023/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41023
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41023
- OSV: https://osv.dev/vulnerability/CVE-2025-41023

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-41023/
Summaries are generated and may contain mistakes; the official description above is the record.