neo4j Enterprise Edition up to 5.26.16/2025.11.1 information exposure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in neo4j Enterprise Edition up to 5.26.16/2025.11.1. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. Such manipulation leads to information exposure. This vulnerability is referenced as CVE-2025-12738. It is possible to launch the attack remotely. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in neo4j Enterprise Edition up to 5.26.16/2025.11.1 and classified as problematic. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a information exposure vulnerability. Using CWE to declare the problem leads to CWE-209. The product generates an error message that includes sensitive information about its environment, users, or associated data. Impacted is confidentiality. CVE summarizes:
Neo4j Enterprise edition versions prior to 2025.11.2 and 5.26.17 are vulnerable to a potential information disclosure by an attacker who has some legitimate access to the database. The vulnerability allows attacker without read access to a property to infer information about its value by trying to enumerate all possible values through observing error messages of SET property. We recommend upgrading to 2025.11.2 or 5.26.17 and above, where the issues is fixed.
The advisory is shared for download at neo4j.com. This vulnerability is handled as CVE-2025-12738 since 11/05/2025. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading to version 5.26.17 or 2025.11.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-4156). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
- 5.26.0
- 5.26.1
- 5.26.2
- 5.26.3
- 5.26.4
- 5.26.5
- 5.26.6
- 5.26.7
- 5.26.8
- 5.26.9
- 5.26.10
- 5.26.11
- 5.26.12
- 5.26.13
- 5.26.14
- 5.26.15
- 5.26.16
- 2025.11.0
- 2025.11.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Information exposureCWE: CWE-209 / CWE-200 / CWE-284
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
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Enterprise Edition 5.26.17/2025.11.2
Timeline
11/05/2025 CVE reserved01/22/2026 Advisory disclosed
01/22/2026 VulDB entry created
01/24/2026 VulDB entry last update
Sources
Advisory: neo4j.comStatus: Confirmed
CVE: CVE-2025-12738 (🔒)
GCVE (CVE): GCVE-0-2025-12738
GCVE (VulDB): GCVE-100-342320
EUVD: 🔒
Entry
Created: 01/22/2026 14:53Updated: 01/24/2026 15:04
Changes: 01/22/2026 14:53 (68), 01/23/2026 12:54 (1), 01/24/2026 15:04 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.