CVE-2026-3582Disclosure(github / enterprise_server)

LOWCVSS 4.3 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

An Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with a classic personal access token (PAT) lacking the repo scope to retrieve issues and commits from private and internal repositories via the search REST API endpoints. The user must have had existing access to the repository through organization membership or as a collaborator for the vulnerability to be exploitable. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.20 and was fixed in versions 3.16.15, 3.17.12, 3.18.6 and 3.19.3. This vulnerability was reported via the GitHub Bug Bounty program.

github CVEs Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-862

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

enterprise_server

Threat summary

3 mentions across 2 observed days
Momentum state: stable

What's happening

Technical details provided in 3 signals
Disclosure: 3 classified signals
Peaked 1d ago at 2 mentions (2026-03-10); latest day: 1
3 total mentions across 2 days

Affected systems

Vendors

github

Products

enterprise_server

Deep dive

Activity timeline3 mentions / 2d

Signal classification1 categories

Disclosure

3100.0%

Referenced assets2 URLs

By indicator

Classification over time

Date	Total	Labels

2026-03-10	2	Disclosure2
2026-03-30	1	Disclosure1

Full discourse3 posts

Vito Botta@vitobotta192d
Disclosure
Found a fascinating bug bounty disclosure in GitHub Enterprise this week. A Personal Access Token that didn't have the repo scope could still retrieve issues and commits from private repositories via search API endpoints. The flaw (CVE-2026-3582) required the attacker to already have legitimate repository access through organisation membership, but it highlights a common problem: token scopes are only as good as the backend code that enforces them. Key lesson for bug bounty hunters: test scope boundaries early and often. Sometimes the permission model has gaps that aren't obvious from the documentation.
Post summary
GitHub Enterprise bug (CVE‑2026‑3582) allows repo‑scope‑restricted tokens to read private repo data via the search API, revealing a scope enforcement flaw; no PoC, exploit code, active threat, or patch discussed.
00001148
895 followersView on X
Infoflowcloud@infoflowcloud211d
Disclosure
🚨*CVE* CVE-2026-3582 An Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with a classic personal access token (PAT) lackin… https://www.cve.org/CVERecord?id=CVE-2026-3582 ----- Traducción: CVE-2026-3582 Se … http://infoflow.cloud`
Post summary
The message announces the discovery of CVE‑2026‑3582, an incorrect authorization bug in GitHub Enterprise Server, and provides a link to the CVE record.
0000030
57 followersView on X
CVE@CVEnew211d
Disclosure
CVE-2026-3582 An Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with a classic personal access token (PAT) lackin… https://www.cve.org/CVERecord?id=CVE-2026-3582
Post summary
The text announces CVE‑2026‑3582, detailing an incorrect authorization issue in GitHub Enterprise Server that can be leveraged by authenticated users with classic PATs. No PoC, exploit, or patch is referenced.
00000227
56.7K followersView on X

CPE platform detail1 entries

Part:

Vendor:

Product:

Version:

Target SW:

Target HW:

1 of 1 entries

Part	Vendor	Product	Version	Target SW	Target HW
App	github	enterprise_server	-	-	-

Explore more

Back to dashboard github CVEs enterprise_server vulnerabilities