CVE-2022-31520: The Luxas98/logstash-management-api repository through 2020-05-04 on GitHub allows absolute path traversal bec

Q: How do I fix CVE-2022-31520?

logstash-management-api: upgrade to newer than 2020-05-04. Exact commands for each OS are on this page.

Q: Is CVE-2022-31520 being exploited?

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

Q: What does CVE-2022-31520 affect?

CVE-2022-31520 affects logstash-management-api. Severity is critical (CVSS 9.3). The Luxas98/logstash-management-api repository through 2020-05-04 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely.

Q: How urgent is CVE-2022-31520?

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

This week

CRITICAL 9.3REMOTEUPGRADE

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

The Luxas98/logstash-management-api repository through 2020-05-04 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

A fixed release or distro patch exists.

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: logstash-management-api 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

logstash-management-api project logstash-management-api UPGRADE

Affected: <= 2020-05-04

Fixed in: newer than 2020-05-04

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy logstash-management-api || rpm -q logstash-management-api || logstash-management-api --version

2. UPGRADE to newer than 2020-05-04 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade logstash-management-api

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade logstash-management-api

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-31520?

logstash-management-api: upgrade to newer than 2020-05-04. Exact commands for each OS are on this page.

Is CVE-2022-31520 being exploited?

CVE-2022-31520 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-31520 affect?

CVE-2022-31520 affects logstash-management-api. Severity is critical (CVSS 9.3). The Luxas98/logstash-management-api repository through 2020-05-04 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely.

How urgent is CVE-2022-31520?

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

Software pages

GitHub vulnerabilities · Kibana and Logstash vulnerabilities · Flask vulnerabilities

References

← Back to latest CVEs