A critical deserialization of untrusted data vulnerability exists in the Station Launcher App of the 3DEXPERIENCE platform from releases R2023x through R2026x. This flaw could allow unauthenticated remote attackers to execute arbitrary code with full system privileges. The vulnerability is identified as CWE-502 and carries a CVSS 3.1 base score of 10.0, indicating maximum severity and impact on confidentiality, integrity, and availability.
Unrolled Secure versions before 1.18.0 have an SSLRedirect bypass vulnerability in the Secure.isSSL() function. This function incorrectly trusts the client-supplied r.URL.Scheme to determine if the transport is HTTPS. An attacker can exploit this by sending plaintext HTTP requests with an absolute-form https:// request-target, bypassing the HTTPS redirect and causing responses to be served unencrypted.
Microsoft jxrlib through version 1.1 and the mircomir jxrlib fork before version 1.3.7 contain a reachable assertion vulnerability in the ParsePFDEntry() function. This vulnerability allows attackers to cause application crashes by supplying a crafted JPEG XR file with an invalid orientation tag. The issue arises from an out-of-range WMP_tagTransformation value that triggers an assertion failure in assertion-enabled builds or results in an unchecked orientation value otherwise.
Microsoft jxrlib through version 1.1 and the mircomir jxrlib fork before 1.3.1 have a NULL pointer dereference vulnerability in the ImageStrDecDecode() function. This occurs when a crafted JPEG XR file declares a color format with no channels, causing a NULL pointer to be dereferenced and crashing the decoder. The vulnerability has a CVSS score of 5.5, indicating medium severity.
Microsoft jxrlib through version 1.1 and the mircomir jxrlib fork before 1.3.6 have a stack buffer over-read vulnerability in the ReadWMIHeader() function. This occurs due to an unterminated signature buffer when processing crafted JPEG XR files with signature bytes containing no zero byte. The flaw can cause strstr to read beyond the stack buffer, potentially crashing the application. The vulnerability has a medium severity with a CVSS score of 5.5 and requires user interaction for exploitation.
Microsoft jxrlib through version 1.1 and the mircomir jxrlib fork before 1.3.1 contain a heap buffer overflow vulnerability in the ReadBinaryData() function. This is caused by an integer overflow of the metadata count, allowing an attacker to supply a crafted JPEG XR file with a large count value that causes an undersized buffer allocation and subsequent heap overflow during file decoding.
Microsoft jxrlib through version 1.1 and the mircomir jxrlib fork before 1.3.1 have a global buffer over-read vulnerability in the initLookupTables() function due to an unchecked bit depth index. This flaw allows attackers to craft a JPEG XR file with an out-of-range bit depth, leading to reading beyond the cbChannels array, which can cause application crashes or memory disclosure.
Microsoft jxrlib through version 1.1 and the mircomir jxrlib fork before 1.3.1 have a global buffer over-read vulnerability in the DecodeSignificantRun() function. This flaw arises from an unchecked run length value in crafted JPEG XR files, which can cause out-of-bounds access leading to memory disclosure or application crashes during image decoding.
The NLTK library's sql_query() function in the chat80 module improperly handles symbolic links when opening SQLite databases. It bypasses the path containment checks enforced by the NLTK data sandbox, allowing an attacker with write access to a trusted NLTK data root to create a symlink pointing to an out-of-sandbox SQLite database. This leads to unauthorized read access to that database's contents. The vulnerability affects NLTK versions from 3.9.4 up to but not including 3.10.4. A fix is available in version 3.10.4.
NLTK's save_maxent_params() and load_maxent_params() functions suffer from a path traversal vulnerability that allows arbitrary file read and write outside the intended directories. This occurs because these functions use the Python built-in open() directly on paths derived from a user-controlled argument without enforcing NLTK's pathsec security checks. The vulnerability bypasses the filesystem sandboxing intended by pathsec.ENFORCE, potentially allowing attackers to read or overwrite files outside permitted directories. The issue affects NLTK versions prior to 3.10.4. A fix has been merged and is included starting from version 3.10.4.
LimeSurvey before 6.17.16+260814 and 7.x before 7.0.10+260813 contains an unauthenticated SQL injection vulnerability in the public statistics page via POST parameter names. Attackers can submit backtick-containing parameter names to buildSelects() and use blind techniques to read administrator password hashes and survey responses on MySQL or MariaDB.
Apache Shiro versions through 3.0.1 have a vulnerability in the PropertiesRealm component where reloading the properties file does not properly remove users or narrow permissions. This can cause removed users and restricted permissions to remain effective until the application is restarted. The issue is fixed in version 3.0.2 and later.
Apache Shiro versions through 3.0.1 have a vulnerability where DefaultPasswordService and SimpleCredentialsMatcher treat an empty stored credential as a match for an empty submitted password. This affects accounts with empty stored credentials. The issue is fixed in version 3.0.2 and later. Alternatively, applications can mitigate by avoiding empty stored credentials and rejecting empty passwords.
A cross-site scripting (XSS) vulnerability exists in Apache Shiro versions through 3.0.1 due to the shiro:principal tags in shiro-web (Jakarta Pages) and shiro-jakarta-ee (Jakarta Faces) not escaping their output. This can allow XSS when principal values are not fully trusted. The issue is resolved in version 3.0.2 and later by escaping the output. Alternatively, input validation of principal values can mitigate the risk.
@fastify/busboy versions 3.2.1 through 3.2.5 contain an off-by-one error in multipart form data parsing that can cause a file attachment part to be misinterpreted as a text field. This occurs when the multipart header terminator sequence is split exactly at the configured header size limit, dropping the final header line. A remote attacker controlling the multipart body can exploit this to bypass upload validation that only applies to file events, potentially allowing malicious payloads to be processed incorrectly. The issue is fixed in version 3.2.6.
@fastify/busboy versions 1.0.0 through 3.2.5 contain a vulnerability in the url-encoded form data parser where a malformed percent escape can cause the decoded field length to bypass the configured per-field size limit. This allows a single unauthenticated field to grow in memory up to the size of the entire request body, potentially leading to excessive memory consumption. The issue is fixed in version 3.2.6.
@fastify/busboy, a multipart form data parser used by Fastify, has a vulnerability in versions 1.0.0 through 3.2.5 where a malformed multipart header causes the parser to hang indefinitely. This leads to request handlers being stalled and resources such as files and database connections leaking until the process is restarted. The same parser issue affects undici versions 5.25.3 through 6.7.0 via formData methods. The issue is fixed in @fastify/busboy version 3.2.6.
@fastify/busboy versions 1.0.0 through 3.2.5 contain a vulnerability where exceeding the configured multipart parts limit causes skipped parts without error listeners. If the request body ends prematurely in such a skipped part, an unhandled error event causes the Node.js process to crash. This allows an unauthenticated attacker to cause a denial of service by sending a crafted request. The issue is fixed in version 3.2.6.
A vulnerability in Apache Shiro version 3.0.1 affects applications that manually create the ShiroFilterFactoryBean and serve static files from case-insensitive filesystems. The fix for CVE-2026-23903 was incomplete, causing path matching to remain case-sensitive by default in these scenarios. Applications using Shiro Spring (Boot) Starter to create the bean are not affected. The issue is resolved in version 3.0.2 or later, or by setting the caseInsensitive property to true on the ShiroFilterFactoryBean.