# CVE-2026-45221: Konga < 2.1.0 Privilege Escalation via Hardcoded OpenSSL Path

> Local attackers can escalate privileges by planting malicious files in a hardcoded path, allowing arbitrary code execution as the launching user.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-cmgw-8j2g-5pmj

## What is CVE-2026-45221?

CVE-2026-45221 is a high-severity vulnerability in EASYBYTE Software Konga, published on 1 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Konga before 2.1.0 contains a privilege escalation vulnerability that allows low-privileged local attackers to execute arbitrary code by planting attacker-controlled OpenSSL configuration or library files in a hardcoded filesystem path absent from default installations. On Windows, the missing directory resides in a location writable by any authenticated local user, enabling attackers to create the directory and place malicious files that execute at the privilege level of the user or service account that launches Konga, facilitating privilege escalation.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-45221 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45221 is a high-severity vulnerability in EASYBYTE Software Konga, published on 1 Sep 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-45221 in the wild and no public exploit code.

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

## Sources

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

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