# CVE-2026-18915: Exposure of OTP Secret Through Process Command-Line Arguments in TÜBİTAK BİLGEM's eta-otp-lock

> Attackers can read OTP secrets from process command-line arguments, enabling system footprinting and potential account compromise.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-2x9j-ppfr-c4pq

## What is CVE-2026-18915?

CVE-2026-18915 is a medium-severity vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute eta-otp-lock, published on 6 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Invocation of process using visible sensitive information vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute eta-otp-lock allows System Footprinting.

This issue affects eta-otp-lock: before 1.0.4.

Weakness: CWE-214 (Invocation of Process Using Visible Sensitive Information)

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


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

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

## Is CVE-2026-18915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18915 is a medium-severity vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute eta-otp-lock, published on 6 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-18915 in the wild and no public exploit code.

Affected product: TÜBİTAK BİLGEM Software Technologies Research Institute eta-otp-lock. 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-18915/ (Markdown: https://insights.sbomify.com/CVE-2026-18915/index.md)
```

## Sources

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

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