Parse Server versions before 8.6.105 and from 9.0.0 up to but not including 9.10.5 contain an ACL bypass vulnerability in $relatedTo relation queries. The server does not properly validate the owning object reference, allowing a client with read access to some objects to infer linked objects it should not have access to. This can disclose relationships between readable and non-readable objects.
Nextcloud versions prior to 32.0.12, 33.0.6, and 34.0.1 have a vulnerability where teams configured as "visible to everyone" prevent non-members from viewing the team via the web UI, but the resources API endpoint still allows authenticated non-members to enumerate the team's internal resources and their identifiers. This exposure does not include access to the contents of those resources, only their existence, names, and identifiers.
Nextcloud versions prior to 32.0.12, 33.0.6, and 34.0.1 allowed app passwords to bypass password confirmation on sensitive endpoints. This vulnerability could permit unauthorized actions on sensitive operations without requiring the user's primary password confirmation.
A vulnerability in Nextcloud's federated share endpoint allows an attacker to write arbitrary rows into the oc_share_external database table. These malicious entries persist indefinitely due to the lack of an automatic cleanup mechanism. This leads to three distinct denial-of-service conditions that can be triggered repeatedly from the same unauthenticated source, renewing every 24 hours as long as the injected rows remain. The issue affects multiple Nextcloud versions prior to fixed releases and has been assigned a high severity rating.
MLflow versions from 3.12.0 up to but not including 3.17.0 contain a critical vulnerability that allows remote code execution via third-party scorer deserialization. This occurs because the system accepts request-selected descendants of allowed modules rather than enforcing exact module restrictions. Unauthenticated deployments are vulnerable to code execution without credentials, while basic-auth deployments require elevated permissions. The vulnerability is fixed in version 3.17.0.
MLflow versions from 2.19.0 up to but not including 3.17.0 have a vulnerability in the CrewAI autologging feature where API keys for large language model providers are recorded in plaintext within logged trace spans. This occurs because the autolog function converts Agent objects to strings including sensitive credentials and expands these into trace inputs, potentially exposing provider API keys to anyone with access to the trace backend or OTLP destination. The issue is fixed in version 3.17.0.
MLflow versions from 3.10.0 up to but not including 3.17.0 contain a vulnerability that allows unauthenticated remote attackers to read arbitrary files on the server. This occurs because the prompt branch in the _create_model_version() function accepts schemeless relative sources without proper path validation. The flaw enables attackers to specify server-local paths as model version artifact locations and retrieve files via the /api/2.0/mlflow/model-versions/get-artifact endpoint. Default unauthenticated servers are fully exposed, while basic-auth deployments are vulnerable to authenticated users with model creation privileges. The issue is fixed in version 3.17.0.
A critical use-after-free vulnerability exists in the replication component of MongoDB Server affecting replica set primary catch-up. This flaw can be triggered by unauthenticated requests and may cause the server to crash or allow arbitrary code execution. The vulnerability impacts replica set members, including shard and config server members in sharded clusters, but not standalone mongod instances. Fixed versions have been released across multiple MongoDB major versions.
ModSecurity versions from 3.0.0 up to but not including 3.0.17 have a vulnerability where response Content-Type header comparisons are case-sensitive. This allows a mixed-case Content-Type that matches a configured lowercase type to bypass response body inspection. As a result, an unauthenticated attacker can receive response content that should be blocked by phase 4 rules, potentially exposing sensitive error or debug information. The issue is fixed in version 3.0.17.
ModSecurity versions prior to 2.9.15 and 3.0.17 contain a vulnerability in the HttpsClient::download function where libcurl's TLS hostname verification is set to a non-strict value. This weakens TLS peer identity validation under adversary-in-the-middle or TLS interception scenarios, potentially allowing acceptance of certificates for unintended hosts. The issue is fixed in versions 2.9.15 and 3.0.17.
MariaDB server versions from 10.11.1 up to but not including 10.11.19, 11.4.1 up to 11.4.13, 11.8.1 up to 11.8.9, 12.3.1 up to 12.3.3, and 13.0.1 up to 13.0.2 contain a vulnerability in the ALTER TABLE ... CONVERT ... PARTITION command. This flaw allows an authenticated user to bypass authorization checks by specifying partition names that require filename escaping, leading to unauthorized access or modification of table files. The issue is fixed in versions 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.
ModSecurity versions from 3.0.0 up to but not including 3.0.17 have a vulnerability in their multipart parser where the RFC 2231 filename* parameter precedence is not applied as done by common backend parsers in Go, Python, Node.js, and Java. This discrepancy allows an attacker to supply a Content-Disposition header with a benign filename parameter for ModSecurity and a different encoded filename* value preferred by the backend, causing the WAF and backend to make security decisions based on different filenames. This can lead to bypassing MULTIPART_FILENAME rules and potentially unsafe file handling by the application. The issue is fixed in version 3.0.17.
A vulnerability in ModSecurity versions 3.0.5 through 3.0.16 causes PCRE2 @rxGlobal match-limit errors to be treated as no-match results rather than errors. This behavior can allow attacker-controlled input to exhaust the SecPcreMatchLimit, preventing certain rules from executing and potentially allowing malicious requests to bypass the WAF. The issue is fixed in version 3.0.17.
A regression in the enforcement of FIPS algorithms in the hashlib module of libpython affects only Python version 3.14.10 when used with OpenSSL in FIPS mode. This issue does not impact other Python versions. A fix is available in Python 3.14.11.
The socket.getaddrinfo() function in libpython versions prior to 3.16.0 accepts embedded null bytes in the host and port parameters, which can cause these values to be silently truncated. This behavior was addressed and fixed in version 3.16.0.
A vulnerability in libpython versions prior to 3.16.0 allows lenient parsing of integers in HTTP response body and chunk framing. This flaw causes incorrect handling of non-hexadecimal or negative integers, potentially leading to misinterpretation of HTTP response contents. The issue is fixed in version 3.16.0.