CVE-2025-3124: Missing Authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized access to private repository names

Published Apr 17, 2025
·
Updated

A missing authorization vulnerability was identified in GitHub Enterprise Server that allowed a user to see the names of private repositories that they wouldn't otherwise have access to in the Security Overview in GitHub Advanced Security. The Security Overview was required to be filtered only using the archived: filter and all other access controls were functioning normally. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.17 and was fixed in versions 3.13.14, 3.14.11, 3.15.6, and 3.16.2.

Affected Software

5 affected components
GitHub Enterprise Server<3.17, >=3.13.14<=3.16.2
GitHub Enterprise Server<3.13.14
GitHub Enterprise Server>=3.14.0<3.14.11
GitHub Enterprise Server>=3.15.0<3.15.6
GitHub Enterprise Server>=3.16.0<3.16.2

Event History

Apr 17, 2025
CVE Published
via MITRE·10:50 PM
Data Sourced
via MITRE·10:50 PM
DescriptionWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-3124?

CVE-2025-3124 is a medium severity vulnerability due to its potential impact on user privacy.

2

How do I fix CVE-2025-3124?

To mitigate CVE-2025-3124, upgrade your GitHub Enterprise Server to a version above 3.17 or between 3.13.14 and 3.16.2.

3

What types of systems are affected by CVE-2025-3124?

CVE-2025-3124 affects GitHub Enterprise Server versions up to exclusive 3.17 and between inclusive 3.13.14 and 3.16.2.

4

What are the consequences of CVE-2025-3124?

If exploited, CVE-2025-3124 allows unauthorized users to view the names of private repositories, compromising user confidentiality.

5

Is there a workaround for CVE-2025-3124?

There are no specific workarounds for CVE-2025-3124; updating the system is the recommended action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203