CVE-2026-1622 (GCVE-0-2026-1622)
Vulnerability from cvelistv5
Published
2026-02-04 09:14
Modified
2026-02-04 15:12
Severity ?
VLAI Severity ?
EPSS score ?
CWE
- CWE-532 - Insertion of Sensitive Information into Log File
Summary
Neo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.
The "obfuscate_literals" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.
We recommend upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had db.logs.query.obfuscate_literals enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting db.logs.query.obfuscate_errors once you have upgraded Neo4j.
References
| URL | Tags | ||||
|---|---|---|---|---|---|
|
|||||
Impacted products
| Vendor | Product | Version | |||||||
|---|---|---|---|---|---|---|---|---|---|
| neo4j | Enterprise Edition |
Version: 2025.01 Version: 5.0 ≤ Version: 4.4 ≤ |
|||||||
|
|||||||||
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-1622",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-02-04T15:12:30.488399Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-02-04T15:12:37.400Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Enterprise Edition",
"vendor": "neo4j",
"versions": [
{
"lessThan": "2026.01.3",
"status": "affected",
"version": "2025.01",
"versionType": "date"
},
{
"lessThan": "5.26.21",
"status": "affected",
"version": "5.0",
"versionType": "semver"
},
{
"lessThan": "4.4.48",
"status": "affected",
"version": "4.4",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://mvnrepository.com/artifact/org.neo4j/",
"defaultStatus": "unaffected",
"packageName": "neo4j",
"product": "Community Edition",
"repo": "https://github.com/neo4j/neo4j",
"vendor": "neo4j",
"versions": [
{
"lessThan": "2026.01.3",
"status": "affected",
"version": "2025.01",
"versionType": "date"
},
{
"lessThan": "5.26.21",
"status": "affected",
"version": "5.0",
"versionType": "semver"
},
{
"lessThan": "4.4.48",
"status": "affected",
"version": "4.4",
"versionType": "semver"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Only applicable if\u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_literals\u0026nbsp;\u003c/code\u003eis enabled"
}
],
"value": "Only applicable if\u00a0db.logs.query.obfuscate_literals\u00a0is enabled"
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:neo4j:enterprise_edition:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2026.01.3",
"versionStartIncluding": "2025.01",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:neo4j:enterprise_edition:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.26.21",
"versionStartIncluding": "5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:neo4j:enterprise_edition:*:*:*:*:*:*:*:*",
"versionEndExcluding": "4.4.48",
"versionStartIncluding": "4.4",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
},
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:neo4j:community_edition:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2026.01.3",
"versionStartIncluding": "2025.01",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:neo4j:community_edition:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.26.21",
"versionStartIncluding": "5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:neo4j:community_edition:*:*:*:*:*:*:*:*",
"versionEndExcluding": "4.4.48",
"versionStartIncluding": "4.4",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003e\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003eNeo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.\u003c/span\u003e\u003cbr\u003e\u003c/p\u003e\u003cp\u003eThe \"obfuscate_literals\" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.\u003c/p\u003e\u003cp\u003eWe recommend\u0026nbsp;upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had\u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_literals\u003c/code\u003e\u0026nbsp;enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting\u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_errors\u0026nbsp;\u003c/code\u003eonce you have upgraded Neo4j.\u003cbr\u003e\u003c/p\u003e"
}
],
"value": "Neo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.\n\n\nThe \"obfuscate_literals\" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.\n\nWe recommend\u00a0upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had\u00a0db.logs.query.obfuscate_literals\u00a0enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting\u00a0db.logs.query.obfuscate_errors\u00a0once you have upgraded Neo4j."
}
],
"impacts": [
{
"capecId": "CAPEC-410",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-410 Information Elicitation"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NO",
"Recovery": "USER",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "LOCAL",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "DIFFUSE",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/AU:N/R:U/V:D/RE:M",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "MODERATE"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-532",
"description": "CWE-532 Insertion of Sensitive Information into Log File",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-02-04T10:02:57.648Z",
"orgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"shortName": "Neo4j"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://neo4j.com/security/CVE-2026-1622"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "We recommend upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had \u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_literals\u003c/code\u003e\u0026nbsp;enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting \u003ccode\u003edb.logs.query.obfuscate_errors \u003c/code\u003eonce you have upgraded Neo4j.\u003cbr\u003e"
}
],
"value": "We recommend upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had \u00a0db.logs.query.obfuscate_literals\u00a0enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting db.logs.query.obfuscate_errors once you have upgraded Neo4j."
}
],
"source": {
"discovery": "INTERNAL"
},
"title": "Unredacted data exposure in query.log",
"x_generator": {
"engine": "Vulnogram 0.5.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
"assignerShortName": "Neo4j",
"cveId": "CVE-2026-1622",
"datePublished": "2026-02-04T09:14:46.320Z",
"dateReserved": "2026-01-29T14:23:26.871Z",
"dateUpdated": "2026-02-04T15:12:37.400Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"cna\": {\"affected\": [{\"defaultStatus\": \"unaffected\", \"product\": \"Enterprise Edition\", \"vendor\": \"neo4j\", \"versions\": [{\"lessThan\": \"2026.01.3\", \"status\": \"affected\", \"version\": \"2025.01\", \"versionType\": \"date\"}, {\"lessThan\": \"5.26.21\", \"status\": \"affected\", \"version\": \"5.0\", \"versionType\": \"semver\"}, {\"lessThan\": \"4.4.48\", \"status\": \"affected\", \"version\": \"4.4\", \"versionType\": \"semver\"}]}, {\"collectionURL\": \"https://mvnrepository.com/artifact/org.neo4j/\", \"defaultStatus\": \"unaffected\", \"packageName\": \"neo4j\", \"product\": \"Community Edition\", \"repo\": \"https://github.com/neo4j/neo4j\", \"vendor\": \"neo4j\", \"versions\": [{\"lessThan\": \"2026.01.3\", \"status\": \"affected\", \"version\": \"2025.01\", \"versionType\": \"date\"}, {\"lessThan\": \"5.26.21\", \"status\": \"affected\", \"version\": \"5.0\", \"versionType\": \"semver\"}, {\"lessThan\": \"4.4.48\", \"status\": \"affected\", \"version\": \"4.4\", \"versionType\": \"semver\"}]}], \"configurations\": [{\"lang\": \"en\", \"supportingMedia\": [{\"base64\": false, \"type\": \"text/html\", \"value\": \"Only applicable if\u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_literals\u0026nbsp;\u003c/code\u003eis enabled\"}], \"value\": \"Only applicable if\\u00a0db.logs.query.obfuscate_literals\\u00a0is enabled\"}], \"cpeApplicability\": [{\"nodes\": [{\"cpeMatch\": [{\"criteria\": \"cpe:2.3:a:neo4j:enterprise_edition:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"2026.01.3\", \"versionStartIncluding\": \"2025.01\", \"vulnerable\": true}, {\"criteria\": \"cpe:2.3:a:neo4j:enterprise_edition:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"5.26.21\", \"versionStartIncluding\": \"5.0\", \"vulnerable\": true}, {\"criteria\": \"cpe:2.3:a:neo4j:enterprise_edition:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"4.4.48\", \"versionStartIncluding\": \"4.4\", \"vulnerable\": true}], \"negate\": false, \"operator\": \"OR\"}, {\"cpeMatch\": [{\"criteria\": \"cpe:2.3:a:neo4j:community_edition:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"2026.01.3\", \"versionStartIncluding\": \"2025.01\", \"vulnerable\": true}, {\"criteria\": \"cpe:2.3:a:neo4j:community_edition:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"5.26.21\", \"versionStartIncluding\": \"5.0\", \"vulnerable\": true}, {\"criteria\": \"cpe:2.3:a:neo4j:community_edition:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"4.4.48\", \"versionStartIncluding\": \"4.4\", \"vulnerable\": true}], \"negate\": false, \"operator\": \"OR\"}], \"operator\": \"OR\"}], \"descriptions\": [{\"lang\": \"en\", \"supportingMedia\": [{\"base64\": false, \"type\": \"text/html\", \"value\": \"\u003cp\u003e\u003cspan style=\\\"background-color: rgb(255, 255, 255);\\\"\u003eNeo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.\u003c/span\u003e\u003cbr\u003e\u003c/p\u003e\u003cp\u003eThe \\\"obfuscate_literals\\\" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.\u003c/p\u003e\u003cp\u003eWe recommend\u0026nbsp;upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had\u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_literals\u003c/code\u003e\u0026nbsp;enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting\u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_errors\u0026nbsp;\u003c/code\u003eonce you have upgraded Neo4j.\u003cbr\u003e\u003c/p\u003e\"}], \"value\": \"Neo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.\\n\\n\\nThe \\\"obfuscate_literals\\\" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.\\n\\nWe recommend\\u00a0upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had\\u00a0db.logs.query.obfuscate_literals\\u00a0enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting\\u00a0db.logs.query.obfuscate_errors\\u00a0once you have upgraded Neo4j.\"}], \"impacts\": [{\"capecId\": \"CAPEC-410\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-410 Information Elicitation\"}]}], \"metrics\": [{\"cvssV4_0\": {\"Automatable\": \"NO\", \"Recovery\": \"USER\", \"Safety\": \"NOT_DEFINED\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"NONE\", \"attackVector\": \"LOCAL\", \"baseScore\": 4.8, \"baseSeverity\": \"MEDIUM\", \"exploitMaturity\": \"NOT_DEFINED\", \"privilegesRequired\": \"LOW\", \"providerUrgency\": \"NOT_DEFINED\", \"subAvailabilityImpact\": \"NONE\", \"subConfidentialityImpact\": \"NONE\", \"subIntegrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"valueDensity\": \"DIFFUSE\", \"vectorString\": \"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/AU:N/R:U/V:D/RE:M\", \"version\": \"4.0\", \"vulnAvailabilityImpact\": \"NONE\", \"vulnConfidentialityImpact\": \"LOW\", \"vulnIntegrityImpact\": \"NONE\", \"vulnerabilityResponseEffort\": \"MODERATE\"}, \"format\": \"CVSS\", \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"problemTypes\": [{\"descriptions\": [{\"cweId\": \"CWE-532\", \"description\": \"CWE-532 Insertion of Sensitive Information into Log File\", \"lang\": \"en\", \"type\": \"CWE\"}]}], \"providerMetadata\": {\"orgId\": \"3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6\", \"shortName\": \"Neo4j\", \"dateUpdated\": \"2026-02-04T10:02:57.648Z\"}, \"references\": [{\"tags\": [\"vendor-advisory\"], \"url\": \"https://neo4j.com/security/CVE-2026-1622\"}], \"solutions\": [{\"lang\": \"en\", \"supportingMedia\": [{\"base64\": false, \"type\": \"text/html\", \"value\": \"We recommend upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had \u0026nbsp;\u003ccode\u003edb.logs.query.obfuscate_literals\u003c/code\u003e\u0026nbsp;enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting \u003ccode\u003edb.logs.query.obfuscate_errors \u003c/code\u003eonce you have upgraded Neo4j.\u003cbr\u003e\"}], \"value\": \"We recommend upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had \\u00a0db.logs.query.obfuscate_literals\\u00a0enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting db.logs.query.obfuscate_errors once you have upgraded Neo4j.\"}], \"source\": {\"discovery\": \"INTERNAL\"}, \"title\": \"Unredacted data exposure in query.log\", \"x_generator\": {\"engine\": \"Vulnogram 0.5.0\"}}, \"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-1622\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-02-04T15:12:30.488399Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-02-04T15:12:33.505Z\"}}]}",
"cveMetadata": "{\"cveId\": \"CVE-2026-1622\", \"assignerOrgId\": \"3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6\", \"state\": \"PUBLISHED\", \"assignerShortName\": \"Neo4j\", \"dateReserved\": \"2026-01-29T14:23:26.871Z\", \"datePublished\": \"2026-02-04T09:14:46.320Z\", \"dateUpdated\": \"2026-02-04T15:12:37.400Z\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…