# CVE-2026-1835: lcg0124 BootDo cross-site request forgery

> Attackers can perform unauthorized actions on behalf of authenticated users in the BootDo web application via cross-site request forgery.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-9pg8-g8f8-c4jx

## What is CVE-2026-1835?

CVE-2026-1835 is a medium-severity vulnerability in lcg0124 BootDo, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was identified in lcg0124 BootDo up to e93dd428ef6f5c881aa74d49a2099ab0cf1e0fcb. This affects an unknown part. The manipulation leads to cross-site request forgery. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-1835 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1835 is a medium-severity vulnerability in lcg0124 BootDo, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1835 in the wild and no public exploit code.

Affected product: lcg0124 BootDo. 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-1835/ (Markdown: https://insights.sbomify.com/CVE-2026-1835/index.md)
```

## Sources

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

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