CVE-2023-0326Public exploitNetwork attack vector

API credential disclosure via unmasked report evidence

Published Mar 27, 2023 · Updated Feb 19, 2025

Information disclosure in GitLab API Security Testing Analyzer 1.6.50 and later before 2.11.0 allows remote attackers to read API credentials. The TokenCheck report generator copies the original Authorization header value into the Evidence field instead of masking it in the generated JSON artifact. An authenticated API scan must use an Authorization header and produce a token-check finding; in a public project, unauthenticated readers can retrieve the artifact and reuse exposed credentials against the tested API.

CVSS severity5.0
Medium
EPSS probability0.80%
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

Information disclosure in GitLab API Security Testing Analyzer 1.6.50 and later before 2.11.0 allows remote attackers to read API credentials. The TokenCheck report generator copies the original Authorization header value into the Evidence field instead of masking it in the generated JSON artifact. An authenticated API scan must use an Authorization header and produce a token-check finding; in a public project, unauthenticated readers can retrieve the artifact and reuse exposed credentials against the tested API.

The record

CVE
CVE-2023-0326
Published
Mar 27, 2023
Updated
Feb 19, 2025
Vendor
GitLab
Product
API Security Testing Analyzer
Classifications
T1552.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 27, 2023CVE publishedPublication date reported by the CVE source.
  2. Feb 19, 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=>=1.6.50, <2.11.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitLab · API Security Testing Analyzerversion=>=1.6.50, <2.11.0

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
5.0GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1552.001Credentials In Files

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