FKIE_CVE-2026-1622

Vulnerability from fkie_nvd - Published: 2026-02-04 10:16 - Updated: 2026-02-04 16:33
Severity ?
4.8 (Medium) - 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
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
3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6https://neo4j.com/security/CVE-2026-1622
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "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."
    },
    {
      "lang": "es",
      "value": "Las versiones de Neo4j Enterprise y Community editions anteriores a 2026.01.3 y 5.26.21 son vulnerables a una potencial revelaci\u00f3n de informaci\u00f3n por parte de un usuario que tiene la capacidad de acceder a los archivos de registro locales.\n\nLa opci\u00f3n \u0027obfuscate_literals\u0027 en los registros de consulta no redacta la informaci\u00f3n de error, exponiendo datos no redactados en el registro de consulta cuando un cliente escribe una consulta que falla. Puede permitir a un usuario con acceso leg\u00edtimo a los archivos de registro locales obtener informaci\u00f3n que no est\u00e1 autorizado a ver. Si este usuario tambi\u00e9n est\u00e1 en posici\u00f3n de ejecutar consultas y activar errores, esta vulnerabilidad puede potencialmente ayudarles a inferir informaci\u00f3n que no est\u00e1n autorizados a ver a trav\u00e9s de su acceso previsto a la base de datos.\n\nRecomendamos actualizar a las versiones 2026.01.3 (o 5.26.21) donde se soluciona el problema, y revisar los permisos de los archivos de registro de consulta para asegurar un acceso restringido. Si su configuraci\u00f3n ten\u00eda \u0027db.logs.query.obfuscate_literals\u0027 habilitado, y desea que la ofuscaci\u00f3n tambi\u00e9n cubra los mensajes de error, debe habilitar la nueva configuraci\u00f3n \u0027db.logs.query.obfuscate_errors\u0027 una vez que haya actualizado Neo4j."
    }
  ],
  "id": "CVE-2026-1622",
  "lastModified": "2026-02-04T16:33:44.537",
  "metrics": {
    "cvssMetricV40": [
      {
        "cvssData": {
          "Automatable": "NO",
          "Recovery": "USER",
          "Safety": "NOT_DEFINED",
          "attackComplexity": "LOW",
          "attackRequirements": "NONE",
          "attackVector": "LOCAL",
          "availabilityRequirement": "NOT_DEFINED",
          "baseScore": 4.8,
          "baseSeverity": "MEDIUM",
          "confidentialityRequirement": "NOT_DEFINED",
          "exploitMaturity": "NOT_DEFINED",
          "integrityRequirement": "NOT_DEFINED",
          "modifiedAttackComplexity": "NOT_DEFINED",
          "modifiedAttackRequirements": "NOT_DEFINED",
          "modifiedAttackVector": "NOT_DEFINED",
          "modifiedPrivilegesRequired": "NOT_DEFINED",
          "modifiedSubAvailabilityImpact": "NOT_DEFINED",
          "modifiedSubConfidentialityImpact": "NOT_DEFINED",
          "modifiedSubIntegrityImpact": "NOT_DEFINED",
          "modifiedUserInteraction": "NOT_DEFINED",
          "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
          "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
          "modifiedVulnIntegrityImpact": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:X",
          "version": "4.0",
          "vulnAvailabilityImpact": "NONE",
          "vulnConfidentialityImpact": "LOW",
          "vulnIntegrityImpact": "NONE",
          "vulnerabilityResponseEffort": "MODERATE"
        },
        "source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-02-04T10:16:04.780",
  "references": [
    {
      "source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
      "url": "https://neo4j.com/security/CVE-2026-1622"
    }
  ],
  "sourceIdentifier": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-532"
        }
      ],
      "source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.