# CVE-2026-85290: InvoicePlane: Log Injection via Unsanitized User Input in Cron Key Error Logging

> Unauthenticated attackers can inject forged log entries via CRLF characters in the cron key, corrupting audit trails and monitoring.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-g53q-v2pv-xr83

## What is CVE-2026-85290?

CVE-2026-85290 is a medium-severity vulnerability in InvoicePlane, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

InvoicePlane is a self-hosted open source application for managing invoices, clients, and payments. Prior to 1.7.2, InvoicePlane's Cron::recur() method writes an invalid cron key from the URL path directly to the application log without neutralizing CRLF characters. An unauthenticated requester can place forged log lines into the audit trail by supplying a crafted cron_key value. The injected entries can corrupt forensic records and interfere with log-based monitoring. This issue is fixed in version 1.7.2.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

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


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

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

## Is CVE-2026-85290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85290 is a medium-severity vulnerability in InvoicePlane, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85290 exists.

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

## Sources

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

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