Leduckhuong

**Name of the Vulnerable Software and Affected Versions** NLTK versions prior to 3.10.3 **Description** Corpus readers reopen root-derived paths using the built-in `open()` function instead of `nltk.pathsec.open()`, which allows symbolic links to escape trusted roots. This path traversal issue enables attackers who place symlinked corpus files within a trusted data root to disclose content located outside that root through corpus reader methods such as `channels()`, `domains()`, and `synonyms()`. Path traversal is a flaw that allows an attacker to access files and directories that are stored outside the web root folder. **Recommendations** Update NLTK to version 3.10.3 or later.

**Name of the Vulnerable Software and Affected Versions** NLTK versions prior to 3.9.4 **Description** A symlink escape issue exists in the `CorpusReader.open()` function. This occurs because path validation is performed lexically and fails to account for symlink resolution. Consequently, a local attacker can place symlinks within the corpus root to read arbitrary files located outside the intended boundary. **Recommendations** Update to version 3.9.4 or later.

**Name of the Vulnerable Software and Affected Versions** NLTK versions prior to 3.10.3 **Description** Allowlisted pickle loaders trust entire module namespaces instead of specific safe callables. This allows attackers to craft malicious pickle payloads that use the pickle REDUCE mechanism to invoke dangerous in-namespace functions, such as `ReppTokenizer. execute` and `numpy.f2py.crackfortran.myeval`, resulting in remote code execution during the loading of model or tokenizer artifacts. **Recommendations** Update NLTK to version 3.10.3.

**Name of the Vulnerable Software and Affected Versions** NocoDB versions prior to 2026.04.1 **Description** An authenticated user with `columnAdd` permission on a Postgres-backed base can perform SQL injection within the formula engine. The issue occurs via the optional `direction` argument of the `ARRAYSORT(...)` function, where the value is not restricted by formula validation and is embedded into a `knex.raw` `ORDER BY` clause. This execution happens during column creation and every subsequent record read of the formula column. The flaw is specific to the Postgres mapping for `ARRAYSORT` in the `packages/nocodb/src/db/functionMappings/pg.ts` file. Technical analysis shows that `ARRAYSORT` fails to enforce an allowlist on the second argument, and the `sanitize()` function in `sqlSanitize.ts` only escapes placeholder characters without validating SQL syntax. This can lead to heavy SQL queries causing multi-second stalls, resulting in a Denial of Service (DoS), or other SQL injection outcomes depending on database permissions. **Recommendations** Update to version 2026.04.1. As a temporary workaround, restrict the `columnAdd` permission to trusted users only to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** NocoDB versions prior to 2026.05.1 **Description** Public shared-view relation endpoints fail to verify if a caller-supplied column ID is visible in the shared view. This allows anyone with a share UUID to read links from any LTAR (Link-To-Another-Record) column on the view's table, including columns hidden by the view owner. The issue exists because the functions `publicMmList()`, `publicHmList()`, and `relDataList()` verified that the column belonged to the view's model but did not check the `show` flag of the view-column entry. Affected API endpoints include: - '/api/v2/public/shared-view/:uuid/rows/:rowId/mm/:columnId' - '/api/v2/public/shared-view/:uuid/rows/:rowId/hm/:columnId' - '/api/v2/public/shared-view/:uuid/rows/:rowId/{ln,om}/:columnId' - '/api/v2/public/shared-view/:uuid/nested/:columnId' **Recommendations** Update to version 2026.05.1.

**Name of the Vulnerable Software and Affected Versions** NLTK versions 3.9.3 and prior **Description** NLTK’s `nltk.app.wordnet app` component allows unauthenticated remote shutdown of the local WordNet Browser HTTP server when started in its default mode. A simple `GET /SHUTDOWN%20THE%20SERVER` request to the ''/SHUTDOWN%20THE%20SERVER'' API endpoint causes the process to terminate immediately via the `os. exit(0)` function, resulting in a denial of service. The vulnerable logic resides in the `nltk/app/wordnet app.py` file, specifically in the `MyServerHandler` class. The server listens on all interfaces and checks for the exact path `SHUTDOWN THE SERVER`. When the `server mode` is set to `False` (the default), the handler directly terminates the process. **Recommendations** Versions prior to 3.9.3 should be updated to a newer version that includes the fix.

**Name of the Vulnerable Software and Affected Versions** NLTK versions 3.9.3 and prior **Description** NLTK (Natural Language Toolkit) contains a reflected cross-site scripting (XSS) issue in the `lookup ...` route of `nltk.app.wordnet app`. A crafted `lookup <payload>` URL can inject arbitrary HTML/JavaScript into the response page because attacker-controlled `word` data is reflected into HTML without proper escaping. This impacts users running the local WordNet Browser server and can lead to script execution in the browser origin of that application. The issue is exploitable because `Reference.decode()` accepts attacker-controlled base64-encoded pickle data for the URL state, and the decoded `word` is reflected into HTML without escaping. The vulnerable code is located in `nltk/app/wordnet app.py` at lines 144, 755, 769, and 796. The API endpoint affected is `/lookup <payload>`. The vulnerable parameter is `word`. **Recommendations** Versions prior to 3.9.3 should be updated to address this issue.