FKIE_CVE-2026-0847

Vulnerability from fkie_nvd - Published: 2026-03-04 19:16 - Updated: 2026-03-05 19:39
Summary
A vulnerability in NLTK versions up to and including 3.9.2 allows arbitrary file read via path traversal in multiple CorpusReader classes, including WordListCorpusReader, TaggedCorpusReader, and BracketParseCorpusReader. These classes fail to properly sanitize or validate file paths, enabling attackers to traverse directories and access sensitive files on the server. This issue is particularly critical in scenarios where user-controlled file inputs are processed, such as in machine learning APIs, chatbots, or NLP pipelines. Exploitation of this vulnerability can lead to unauthorized access to sensitive files, including system files, SSH private keys, and API tokens, and may potentially escalate to remote code execution when combined with other vulnerabilities.
Impacted products
Vendor Product Version

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "A vulnerability in NLTK versions up to and including 3.9.2 allows arbitrary file read via path traversal in multiple CorpusReader classes, including WordListCorpusReader, TaggedCorpusReader, and BracketParseCorpusReader. These classes fail to properly sanitize or validate file paths, enabling attackers to traverse directories and access sensitive files on the server. This issue is particularly critical in scenarios where user-controlled file inputs are processed, such as in machine learning APIs, chatbots, or NLP pipelines. Exploitation of this vulnerability can lead to unauthorized access to sensitive files, including system files, SSH private keys, and API tokens, and may potentially escalate to remote code execution when combined with other vulnerabilities."
    },
    {
      "lang": "es",
      "value": "Una vulnerabilidad en versiones de NLTK hasta la 3.9.2 inclusive permite la lectura arbitraria de archivos a trav\u00e9s de salto de ruta en m\u00faltiples clases CorpusReader, incluyendo WordListCorpusReader, TaggedCorpusReader y BracketParseCorpusReader. Estas clases no logran sanear o validar correctamente las rutas de archivo, permitiendo a los atacantes recorrer directorios y acceder a archivos sensibles en el servidor. Este problema es particularmente cr\u00edtico en escenarios donde se procesan entradas de archivo controladas por el usuario, como en APIs de aprendizaje autom\u00e1tico, chatbots o pipelines de PNL. La explotaci\u00f3n de esta vulnerabilidad puede conducir al acceso no autorizado a archivos sensibles, incluyendo archivos del sistema, claves privadas SSH y tokens de API, y puede escalar potencialmente a ejecuci\u00f3n remota de c\u00f3digo cuando se combina con otras vulnerabilidades."
    }
  ],
  "id": "CVE-2026-0847",
  "lastModified": "2026-03-05T19:39:11.967",
  "metrics": {
    "cvssMetricV30": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 8.6,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L",
          "version": "3.0"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 4.7,
        "source": "security@huntr.dev",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-03-04T19:16:10.683",
  "references": [
    {
      "source": "security@huntr.dev",
      "url": "https://huntr.com/bounties/fc69914f-36a9-4c18-8503-10013b39f966"
    }
  ],
  "sourceIdentifier": "security@huntr.dev",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-22"
        }
      ],
      "source": "security@huntr.dev",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…