# CVE-2026-105040: EnergizeLab Eilik User-ID Mass Assignment Account Takeover

> A registered user can take over another account by manipulating the user ID in update requests due to mass assignment in the NestJS auth service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-49rf-m9q2-2xm2

## What is CVE-2026-105040?

CVE-2026-105040 is a high-severity authentication bypass vulnerability in EnergizeLab NestJS auth service, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The EnergizeLab Eilik NestJS auth service accepts a user-controlled user ID in account update requests (mass assignment). A registered user can set another account's identifier and take over that account.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-105040?


## How do I fix CVE-2026-105040?

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

## Is CVE-2026-105040 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105040 and fix it if it is affected.

What it is: CVE-2026-105040 is a high-severity authentication bypass vulnerability in EnergizeLab NestJS auth service, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105040 in the wild and no public exploit code.

Affected product: EnergizeLab NestJS auth service. 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-2026-105040/ (Markdown: https://insights.sbomify.com/CVE-2026-105040/index.md)
```

## Sources

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

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