Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-1561: Lura and KrakenD-CE versions older than v2.0.2 and KrakenD-EE versions older than v2.0.0 do not sanitize URL p

31
Routine
MEDIUM 4.0REMOTEUPGRADEUPGRADE

CVE-2022-1561 is a medium-severity flaw (CVSS 4.0) affecting krakend, lura. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Lura and KrakenD-CE versions older than v2.0.2 and KrakenD-EE versions older than v2.0.0 do not sanitize URL parameters correctly, allowing a malicious user to alter the backend URL defined for a pipe when remote users send crafty URL requests. The vulnerability does not affect KrakenD itself, but the consumed backend might be vulnerable.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score4.0 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 52%)
CISA exploited listNo
WeaknessCWE-471
Published2022-08-01
Last modified2026-06-17
Publisher (CNA): Spanish National Cybersecurity Institute, S.A. (INCIBE) · Vendor: krakend · luraproject

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

krakend krakend UPGRADE
Affected: < 2.0.0 · <= 2.0.2
Fixed in: 2.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy krakend || rpm -q krakend || krakend --version
2. UPGRADE to 2.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade krakend
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade krakend
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
luraproject lura UPGRADE
Affected: < 2.0.2
Fixed in: 2.0.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy lura || rpm -q lura || lura --version
2. UPGRADE to 2.0.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade lura
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade lura
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-1561?

krakend: upgrade to 2.0.0; lura: upgrade to 2.0.2. Exact commands for each OS are on this page.

Is CVE-2022-1561 being exploited?

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

CVE-2022-1561 affects krakend, lura. Severity is medium (CVSS 4.0). Lura and KrakenD-CE versions older than v2.0.2 and KrakenD-EE versions older than v2.0.0 do not sanitize URL parameters correctly, allowing a malicious user to alter the backend URL defined for a pipe when remote users send crafty URL reque

How urgent is CVE-2022-1561?

Priority 31/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.