Mintlify Platform prior 2025-11-15 GitHub Integration API Name direct request
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Mintlify Platform. The affected element is an unknown function of the component GitHub Integration API. The manipulation of the argument Name leads to direct request. This vulnerability is documented as CVE-2025-67844. The attack can be initiated remotely. There is not any exploit available. This product is a managed service, therefore users are not responsible for maintaining vulnerability countermeasures. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Mintlify Platform and classified as problematic. This issue affects an unknown functionality of the component GitHub Integration API. The manipulation of the argument name with an unknown input leads to a direct request vulnerability. Using CWE to declare the problem leads to CWE-425. The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files. Impacted is confidentiality. The summary by CVE is:
The GitHub Integration API in Mintlify Platform before 2025-11-15 allows remote attackers to obtain sensitive repository metadata via the repository owner and name fields. It fails to validate that the repository owner and name fields provided during configuration belong to the specific GitHub App Installation ID associated with the user's organization.
The advisory is shared at mintlify.com. The identification of this vulnerability is CVE-2025-67844 since 12/12/2025. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 2025-11-15 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Managed Service
- yes
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
CNA Base Score: 5.0
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Direct requestCWE: CWE-425
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Status: 🔍0-Day Time: 🔒
Upgrade: Platform 2025-11-15
Timeline
11/15/2025 Countermeasure disclosed12/12/2025 CVE reserved
12/19/2025 Advisory disclosed
12/19/2025 VulDB entry created
01/02/2026 VulDB entry last update
Sources
Advisory: mintlify.comStatus: Confirmed
CVE: CVE-2025-67844 (🔒)
GCVE (CVE): GCVE-0-2025-67844
GCVE (VulDB): GCVE-100-337541
Entry
Created: 12/19/2025 08:15Updated: 01/02/2026 19:25
Changes: 12/19/2025 08:15 (66), 01/02/2026 19:25 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.