# CVE-2026-12673: Privilege escalation in liquidfiles

> An Admin in a secondary domain can escalate privileges to Sysadmin by modifying a group in their managed secondary group.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-pmp7-7j9c-794v

## What is CVE-2026-12673?

CVE-2026-12673 is a medium-severity vulnerability in liquidfiles, published on 20 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Liquidfiles versions before 4.2.12 are affected by a broken access control vulnerability resulting in privilege escalation from an Admin in a secondary domain to a Sysadmin by modifying a group in their managed secondary (non-default) group.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-12673 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12673 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12673 is a medium-severity vulnerability in liquidfiles, published on 20 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12673 exists.

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

## Sources

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

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