Arbitrary Code Injection Affecting label-studio package, versions <1.23.1-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-LABELSTUDIO-20416338
- published4 Oct 2026
- disclosed4 Jul 2026
Introduced: 4 Jul 2026
CVE-2026-12252 (opens in a new tab)How to fix?
Upgrade Minimos:latest label-studio to version 1.23.1-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream label-studio package and not the label-studio package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
In nltk/nltk versions 3.9.3 and earlier, five Stanford interface classes (StanfordPOSTagger, StanfordNERTagger, StanfordParser, StanfordDependencyParser, and StanfordNeuralDependencyParser) are vulnerable to untrusted JAR code execution. These classes accept user-controllable JAR paths and execute them via the java() function, which invokes subprocess.Popen() without integrity verification. This vulnerability is identical to CVE-2026-0848, which was fixed for StanfordSegmenter by adding SHA256 verification. However, the fix was not applied to these additional classes, leaving them susceptible to arbitrary code execution when loading untrusted JAR files.