# CVE-2026-12504: Loytec LINX firmware: Improper Authentication in PAM configuration

> Local attackers can gain root access without a password due to improper PAM configuration in Loytec LINX devices.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-6gf2-c64f-3g3h

## What is CVE-2026-12504?

CVE-2026-12504 is a high-severity authentication bypass vulnerability in Loytec L-DALI, published on 24 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Authentication (CWE-287) in the PAM configuration in Loytec LIP-ME201C, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS and L-PAD through 8.4.16 on LINX-A64 allows a local attacker to authenticate as a uid=0 account without a password and obtain a root shell via an `/etc/passwd` entry with an empty password field.

Weakness: CWE-521 (Weak Password Requirements), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-12504 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12504 is a high-severity authentication bypass vulnerability in Loytec L-DALI, published on 24 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12504 in the wild and no public exploit code.

Affected product: Loytec L-DALI. 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-12504/ (Markdown: https://insights.sbomify.com/CVE-2026-12504/index.md)
```

## Sources

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

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