CVE-2022-3486Public exploitNetwork attack vector

OAuth token theft via chained open redirects

Published Nov 9, 2022 · Updated May 1, 2025

Open redirect in affected GitLab CE/EE releases allows remote attackers to redirect users to arbitrary sites through crafted URLs. Jira DVCS routes prepend a slash to a decoded project path, while a deprecated repository route accepts traversal segments without validation, enabling chained redirects. A user must trust the URL and complete the OAuth flow; affected releases are 9.4 through 15.3.4, 15.4 through 15.4.3, and 15.5 through 15.5.1, and the chain exposes an OAuth access token that enables account takeover.

CVSS severity6.1
Medium
EPSS probability0.78%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Open redirect in affected GitLab CE/EE releases allows remote attackers to redirect users to arbitrary sites through crafted URLs. Jira DVCS routes prepend a slash to a decoded project path, while a deprecated repository route accepts traversal segments without validation, enabling chained redirects. A user must trust the URL and complete the OAuth flow; affected releases are 9.4 through 15.3.4, 15.4 through 15.4.3, and 15.5 through 15.5.1, and the chain exposes an OAuth access token that enables account takeover.

The record

CVE
CVE-2022-3486
Published
Nov 9, 2022
Updated
May 1, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-601, T1528
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 9, 2022CVE publishedPublication date reported by the CVE source.
  2. May 1, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=15.4, <15.4.4
  2. Affected versionversion=>=15.5, <15.5.2
  3. Affected versionversion=>=9.4, <15.3.5

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitLab · GitLabversion=>=15.4, <15.4.4; version=>=15.5, <15.5.2; version=>=9.4, <15.3.5

Published CVSS scores

6.1NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-601URL Redirection to Untrusted Site ('Open Redirect')
T1528Steal Application Access Token

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo