# CVE-2022-40083: Labstack Echo Open Redirect vulnerability

> Attackers can exploit an open redirect in the Static Handler to trigger Server-Side Request Forgery, bypassing security controls.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** DEBIAN-CVE-2022-40083, GHSA-crxj-hrmp-4rwf, GO-2022-1031, UBUNTU-CVE-2022-40083

## What is CVE-2022-40083?

CVE-2022-40083 is a critical vulnerability in n/a, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Labstack Echo v4.8.0 was discovered to contain an open redirect vulnerability via the Static Handler component. This vulnerability can be leveraged by attackers to cause a Server-Side Request Forgery (SSRF).

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2022-40083?

3 open source packages ship an affected version, including github.com/labstack/echo/v4. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/labstack/echo/v4` | Go | All versions | 4.9.0 |
| `github.com/labstack/echo/v4` | Go | All versions | 4.9.0 |
| `github.com/labstack/echo/v4` | Go | All versions | 4.9.0 |

Products: Labstack Echo.

## How do I fix CVE-2022-40083?

Upgrade github.com/labstack/echo/v4 to 4.9.0 or later.

## Is CVE-2022-40083 being exploited?

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

Public exploit code:

- Labstack Echo 4.8.0 - Open Redirect (nuclei): http/cves/2022/CVE-2022-40083.yaml

## Other vulnerabilities in n/a

- [CVE-2026-25766](https://insights.sbomify.com/CVE-2026-25766/): Echo has a Windows path traversal via backslash in middleware.Static default filesystem (medium 5.3)
- [CVE-2020-36565](https://insights.sbomify.com/CVE-2020-36565/): Directory traversal on Windows in github.com/labstack/echo/v4 (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40083 and fix it if it is affected.

What it is: CVE-2022-40083 is a critical vulnerability in n/a, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40083 exists.

Affected packages and fixed versions:
- github.com/labstack/echo/v4 (Go): affected all versions; fixed in 4.9.0
- github.com/labstack/echo/v4 (Go): affected all versions; fixed in 4.9.0
- github.com/labstack/echo/v4 (Go): affected all versions; fixed in 4.9.0

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-2022-40083/ (Markdown: https://insights.sbomify.com/CVE-2022-40083/index.md)
```

## Sources

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

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