CVE-2022-3060Public exploitNetwork attack vector

Victim-authorized PUT requests via unsanitized error IDs

Published Oct 17, 2022 · Updated May 13, 2025

Resource injection in GitLab CE/EE allows remote authenticated users to induce arbitrary PUT requests through a victim's session. Error Tracking accepts an unvalidated Sentry error ID and concatenates it into action-button URLs, letting traversal segments redirect an Axios PUT to another GitLab API path. A project Maintainer or Owner must configure a spoofed Sentry backend and persuade a signed-in victim to click Ignore or Resolve; the request can change any resource the victim may modify, including granting administrator status when the victim is an administrator.

CVSS severity7.3
High
EPSS probability0.98%
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

Resource injection in GitLab CE/EE allows remote authenticated users to induce arbitrary PUT requests through a victim's session. Error Tracking accepts an unvalidated Sentry error ID and concatenates it into action-button URLs, letting traversal segments redirect an Axios PUT to another GitLab API path. A project Maintainer or Owner must configure a spoofed Sentry backend and persuade a signed-in victim to click Ignore or Resolve; the request can change any resource the victim may modify, including granting administrator status when the victim is an administrator.

The record

CVE
CVE-2022-3060
Published
Oct 17, 2022
Updated
May 13, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-22, T1204
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 17, 2022CVE publishedPublication date reported by the CVE source.
  2. May 13, 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=>=12.7, <15.2.5
  2. Affected versionversion=>=15.3, <15.3.4
  3. Affected versionversion=>=15.4, <15.4.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=12.7, <15.2.5; version=>=15.3, <15.3.4; version=>=15.4, <15.4.1

Published CVSS scores

7.3GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
T1204User Execution

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