CVE-2025-12738: neo4j Enterprise Edition · Information Exposure
Affects neo4j Enterprise EditionSource CVE Database V5
Not known to be exploited · CVSS 1.3 Low : upgrade to 2025.11.2 or 5.26.17 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2025.11.2, 5.26.17
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/V:DExploitation evidence
Disclosed: evidence found.
CVE published 22 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade neo4j Enterprise Edition to 2025.11.2 or 5.26.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| neo4jEnterprise Edition | Affected
| Fixed in
|
| neo4jEnterprise Edition | Affected
| Fixed in
|
AI-suggested
- Upgrade Neo4j Enterprise Edition to version 2025.11.2 or 5.26.17 or later, where the vulnerability is fixed.
- Review and tighten database access controls to minimize the number of users with any level of access, especially those with write permissions that could be exploited for enumeration.
- Implement monitoring and alerting for unusual SET property operations or repeated failed attempts that could indicate enumeration activity.
- Consider application-layer controls to limit the exposure of detailed error messages to authenticated users, potentially customizing error handling to avoid leaking sensitive information.
- Conduct regular audits of database permissions and logs to detect potential misuse.
- Educate database administrators and developers about the risks of information leakage through error messages and encourage secure coding and configuration practices.
Description
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.