CVE-2022-31519: The Lukasavicus/WindMill repository through 1.0 on GitHub allows absolute path traversal because the Flask sen

This week

CRITICAL 9.3REMOTEDOWNGRADE

CVE-2022-31519 is a critical-severity flaw (CVSS 9.3) affecting windmill. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Lukasavicus/WindMill repository through 1.0 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.3 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Weakness	CWE-22
Published	2022-07-11
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: windmill project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-07-11 01:15 UTCPublished CVE record published
2026-06-17 04:45 UTCUpdated Record last modified

windmill project windmill DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy windmill || rpm -q windmill || windmill --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison windmill sudo apt install windmill=<VERSION_BEFORE_1.0> sudo apt-mark hold windmill

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list windmill sudo dnf downgrade windmill-<VERSION_BEFORE_1.0> sudo dnf versionlock add windmill

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-31519?

windmill: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-31519 being exploited?

CVE-2022-31519 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-31519 affect?

CVE-2022-31519 affects windmill. Severity is critical (CVSS 9.3). The Lukasavicus/WindMill repository through 1.0 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely.

How urgent is CVE-2022-31519?

Priority 60/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities · Flask vulnerabilities

Related CVEs

CVE-2026-22683 HIGH 8.8 UPGRADE UPGRADE Windmill versions 1.56.0 through 1.614.0 contain a missing authorization vulnerability that allows users with
CVE-2026-33881 HIGH 7.2 UPGRADE Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs
CVE-2026-29059 HIGH 7.5 UPGRADE Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs
CVE-2026-26964 LOW 2.7 UPGRADE Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs

References

← Back to latest CVEs