CVE-2026-25729
Unknown Unknown - Not Provided
Improper Access Control in DeepAudit /api/v1/users Endpoint Exposes Sensitive Data

Publication date: 2026-02-06

Last updated on: 2026-04-29

Assigner: GitHub, Inc.

Description
DeepAudit is a multi-agent system for code vulnerability discovery. In 3.0.4 and earlier, there is an improper access control vulnerability in the /api/v1/users/ endpoint allows any authenticated user to enumerate all users in the system and retrieve sensitive information including email addresses, phone numbers, full names, and role information.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-06
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-02-06
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
lintsinghua deepaudit to 3.0.4 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-25729 is an improper access control vulnerability in DeepAudit versions 3.0.4 and earlier, specifically in the /api/v1/users/ endpoint.

This vulnerability allows any authenticated user to enumerate all users in the system and retrieve sensitive information such as email addresses, phone numbers, full names, and role information.

The root cause is that the endpoint only verifies that a user is logged in but does not enforce authorization checks like requiring administrative privileges.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive user information to any authenticated user.

  • Exposure of email addresses, phone numbers, full names, and role information of all users in the system.
  • Potential privacy violations and increased risk of targeted attacks such as phishing or social engineering.

Although the severity is rated low, the exposure of sensitive user data can have significant privacy and security implications.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by attempting to access the /api/v1/users/ endpoint with any authenticated user account and checking if sensitive user information such as email addresses, phone numbers, full names, and role information is returned.'}, {'type': 'paragraph', 'content': 'A simple detection method is to use a command-line tool like curl to send an authenticated GET request to the endpoint and observe the response.'}, {'type': 'list_item', 'content': 'curl -H "Authorization: Bearer <token>" https://<target-system>/api/v1/users/'}, {'type': 'paragraph', 'content': 'If the response contains a list of users with sensitive details, the system is vulnerable.'}] [2]

Mitigation Strategies

The immediate mitigation step is to upgrade DeepAudit to version 3.0.5 or later, where the vulnerability is patched.

The patch restricts access to the /api/v1/users/ endpoint to only active superusers by changing the dependency from get_current_user to get_current_active_superuser.

If upgrading is not immediately possible, restrict access to the vulnerable endpoint by network controls or API gateway rules to allow only trusted administrative users.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-25729. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart