A security flaw exists in libimobiledevice up to version 1.4.0 in the afc_get_device_info_key function of src/afc.c. This vulnerability involves memory corruption triggered by manipulating the argument Value. Exploitation requires local access. Public exploit code has been released, but the vendor has not responded to the disclosure. The CVSS score is 5.3, indicating a medium severity.
A heap-based buffer overflow vulnerability exists in libimobiledevice up to version 1.4.0 in the src/afc.c component (AFC). This vulnerability can be exploited remotely and has publicly available exploit code. The vendor has not responded to the disclosure. The CVSS score is 6.3 (medium severity).
A buffer overflow vulnerability exists in the Brotli decoder component of Google Brotli versions 1.0.3 through 1.2.0. This flaw allows remote unauthenticated attackers to corrupt adjacent memory, potentially leading to sensitive data disclosure, denial of service, or arbitrary code execution. Users should update affected Brotli libraries or binaries to fixed versions 1.0.10, 1.1.1, or 1.2.1. Additionally, the vulnerability affects the locust product in versions >=2.2.1 <2.18.4 and >=2.23.1 <2.47.0_1, with fixes available in 2.18.4 and 2.47.0_1.
A vulnerability in virtualenv's xonsh activation script allows attacker-controlled prompt text to become executable code during environment activation if the xonsh source encoding is a legacy multibyte encoding such as GBK or Big5. This occurs because the activation script is written in UTF-8 but read with a different codec, causing misinterpretation of escape sequences and enabling code injection. The issue affects POSIX activation scripts and requires an attacker to control the prompt or destination argument passed to virtualenv, with the user subsequently activating the environment. The vulnerability is fixed in virtualenv version 1.18.1_2.
CVE-2026-113717 is a vulnerability in virtualenv's pip seeder when used with the --download option. The issue arises because the pip seeder downloads bundled wheels with download=False, skipping virtualenv's wheel digest verification. This allows an attacker controlling a package index to serve a modified pip wheel that virtualenv installs without verifying its integrity. Both --seeder pip and --download options must be enabled for exploitation. A fix is available in virtualenv version 1.18.1_2.
CVE-2026-113714 is a vulnerability in virtualenv's wheel download and caching mechanism where downloaded wheel files are placed directly into the reusable wheel cache before verification. The verification process selects the file to check based on pip's textual output rather than the actual downloaded file, allowing an attacker-controlled package index to inject forged output lines. This can cause a modified wheel to be cached and reused despite failing verification, potentially leading to the use of tampered packages in new environments. The issue does not bypass TLS or affect the default PyPI setup and requires a custom index with digest verification enabled. A fix was released in virtualenv version 1.18.1_2 that downloads wheels to a temporary location and only promotes them to the cache after successful verification.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Camel Docling component.
This issue affects Apache Camel: from 4.15.0 before 4.18.5, from 4.19.0 before 4.22.2.
DoclingProducer runs the external docling tool in CLI mode, the default, and tells it where to write the converted document through the --output flag. When the CamelDoclingOutputFilePath header was set, addOutputDirectoryArguments handed its value to that flag verbatim: the value was not normalized, an absolute path or a path containing .. segments was accepted as given, and no endpoint option could confine it to a directory. The custom-argument validation added by the fix for CVE-2026-40047 refuses the --output and -o flags in the CamelDoclingCustomArguments header and tells callers to choose the output directory with this header instead, so the one value that decides where docling writes reached the command line without any of the checks applied to custom arguments. Docling writes the conversion result, as Markdown, HTML, JSON or text, into that directory, naming the file after the input file, and the producer afterwards removes only its own temporary directory, so the file is left in place. A party able to set the header could therefore have conversion output created in any directory the Camel process can write to. The content of such a file is the conversion of the document carried by the message, so it is shaped by whoever supplies that document without being written byte for byte, and when the document content arrives in the message body the producer stores it under a random temporary name, which the output file then carries. The header belongs to the Camel header namespace, which consumers applying Camel's default header filtering, such as the JMS and Kafka consumers, remove from incoming messages, so the issue is reached where a route forwards externally influenced values into the header or where a consumer maps incoming headers without that filtering. The docling-serve mode does not use the header.
Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.2. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The fix adds an outputBaseDirectory endpoint option that is unset by default, so after upgrading, set it on every docling endpoint whose CamelDoclingOutputFilePath header can carry a value influenced from outside the deployment; without it the header is normalized but can still name any directory. The 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. For deployments that cannot upgrade immediately, do not build the CamelDoclingOutputFilePath header from values that originate outside the deployment, remove that header from messages that arrive from outside before they reach a docling endpoint, and make sure that consumers which map incoming message headers drop the Camel header namespace, so that only the route itself chooses the output directory.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Camel Docling component.
This issue affects Apache Camel: from 4.15.0 before 4.18.5, from 4.19.0 before 4.22.2.
DoclingProducer builds the command line of the external docling tool and appends to it the custom arguments supplied in the CamelDoclingCustomArguments header, a list of strings whose flags the fix for CVE-2026-40047 restricted to an allowlist. That fix also introduced validatePathSafety to keep path-like argument values inside the intended directory, but the method only looked for relative traversal: it rejected a value containing a traversal sequence such as ../ and a value whose normalized form still held a .. element. It never checked whether a value was an absolute path, and an absolute path without traversal segments contains neither, so it passed unchanged. Every path-like value went through this check, whether it was a separate list element following its flag or was attached to the flag after an equals sign, so an absolute path was accepted in either form, for example as the directory given to the allowlisted --artifacts-path flag, which tells docling where to find its model artifacts. Such a value reached the docling command line as given, so a party able to choose the custom arguments could point the docling process at any directory the Camel process can access, outside the working directory that the check was meant to keep path values in, which is the outcome the CVE-2026-40047 fix set out to prevent. Only the CLI mode, which is the default, passes custom arguments to docling. The header belongs to the Camel header namespace, which consumers applying Camel's default header filtering, such as the JMS and Kafka consumers, remove from incoming messages, so the issue is reached where a route forwards externally influenced values into the header or where a consumer maps incoming headers without that filtering.
Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.2. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. For deployments that cannot upgrade immediately, do not build the CamelDoclingCustomArguments header from values that originate outside the deployment, remove that header from messages that arrive from outside before they reach a docling endpoint, and make sure that consumers which map incoming message headers drop the Camel header namespace, so that only the route itself chooses the custom arguments.
CVE-2026-95663 is an insufficient session expiration vulnerability in the Apache Camel Keycloak component affecting versions from 4.16.0 before 4.18.5 and from 4.19.0 before 4.22.2. When token introspection is enabled, the component caches token introspection results without respecting the token's expiration time, allowing expired tokens to be accepted for up to the cache's time-to-live. This can permit continued use of recently expired tokens for a short window, but does not allow token forgery or privilege escalation. The issue is fixed in Apache Camel versions 4.18.5 and 4.22.2.
CVE-2026-95664 is an Expression Language Injection vulnerability in the Apache Camel AWS2-s3 component affecting versions from 4.8.0 before 4.18.5 and from 4.19.0 before 4.22.2. The issue arises because the key used by the aws2-s3 producer is taken from a message header and evaluated as a Simple language expression if it contains certain markers, allowing untrusted input to be executed. This can lead to unauthorized access to JVM system properties, environment variables, and invocation of methods on beans, potentially exposing sensitive information. The vulnerability is fixed in versions 4.18.5 and 4.22.2. Users are advised to upgrade to these versions or 4.23.0 or later. Workarounds include removing or validating the CamelAwsS3Key header to prevent untrusted expressions from being evaluated.
CVE-2026-101259 is a vulnerability in the Apache Camel CoAP component affecting versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.2. It allows generation of error messages containing sensitive internal information such as class names, file paths, host names, and connection details. This occurs when the CoAP consumer fails to build its response after route completion and returns detailed exception messages in a 5.00 Internal Server Error response. The issue is fixed in Apache Camel versions 4.18.5, 4.22.2, and later 4.23.0. Users are advised to upgrade to these fixed versions to prevent sensitive information disclosure.
A heap-based buffer overflow vulnerability exists in the ole_info_read_metabat function of the OLE2 Parser component in GNOME libgsf up to version 1.14.60. This vulnerability can be triggered remotely and may lead to limited confidentiality, integrity, and availability impacts. A patch identified by commit a8e25560b74f84c3f86df6ca0ac59195fa5af68a is recommended to fix the issue.
The python313-djangorestframework-3.18.2-1.1 package on the GA media of openSUSE Tumbleweed addresses multiple security issues. These vulnerabilities have been fixed in this package version. No specific details about the nature of the vulnerabilities or their impact are provided.
Starman versions before 0.4019 for Perl incorrectly send response bodies for HEAD requests, causing desynchronization of responses on keep-alive connections. This includes responses with status codes 1xx, 204, or 304, which also carry a body improperly. As a result, clients may misinterpret response data, and front-end proxies reusing upstream connections may associate responses with incorrect requests.
Starman versions before 0.4019 for Perl have a vulnerability where a stalled request body can indefinitely hold a worker thread, causing denial of service. This occurs because the read_timeout setting only applies to headers, while the body is read with blocking calls without a deadline. An attacker can exploit this by sending complete headers and then stalling or trickling the request body, tying up workers until they disconnect. Version 0.4019 introduces fixes by applying read_timeout to body reads and adding a body_timeout limit of 300 seconds.
Rclone versions from 1.64.0 up to but not including 1.75.2 contain an authentication bypass vulnerability in the serve webdav feature. This flaw allows unauthenticated attackers to bypass authentication by sending OPTIONS requests. Exploitation enables attackers to probe arbitrary paths and use the Allow header values to determine the existence of files or collections, facilitating namespace enumeration.