Traefik versions before 2.11.46, 3.x before 3.6.17, and version 3.7.0 have a vulnerability in the Kubernetes Ingress provider where namespace validation is missing for Ingress and Service annotations. This allows an attacker with permissions to create or update Ingress or Service resources in one namespace to reference Middlewares, ServersTransports, and TLSOptions in other namespaces. Such a flaw can lead to bypassing namespace-based tenant isolation by accessing another tenant's injected credentials or reusing its client certificates.
MLflow 3.17.1 and earlier contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by submitting a crafted trace ID containing traversal sequences to the POST /api/3.0/mlflow/traces endpoint. Attackers can exploit FileStore.start_trace() to write trace_info.yaml, request_metadata, and tag files with attacker-controlled metadata outside the intended experiment trace directory, subject to the server process's filesystem permissions. FileStore is the default tracking backend before MLflow 3.7.0 and opt-in thereafter (the default changed to a SQLite database), so deployments in the earlier part of the affected range are vulnerable without special configuration while later ones are affected only when FileStore is explicitly selected.
CVE-2026-109433 is an authorization bypass vulnerability in Camunda 7's Cockpit webapp affecting versions 7.23.0 before 7.23.17 and 7.24.0 before 7.24.16. The flaw arises from inverted comparison logic in permission checks, allowing authenticated users with minimal access to read all process instances, definitions, and incidents engine-wide without logging. This vulnerability has a medium severity score and is fixed in versions 7.23.17 and 7.24.16.
Camunda 7.24.0 before 7.24.14 and 7.23.0 before 7.23.17 contains an expression injection vulnerability where AdhocQueryValidator.validate() fails to check sub-query expression maps within the orQueries field exposed by TaskQueryDto, allowing authenticated users to bypass the enableExpressionsInAdhocQueries restriction. Attackers can supply a malicious JUEL expression such as dueAfterExpression inside an orQueries entry to achieve arbitrary Java reflection and invoke java.lang.Runtime.exec, resulting in operating-system command execution as the engine service user.
Camunda 7.24.0 before 7.24.14 and 7.23.0 before 7.23.17 contains a missing authorization check vulnerability in engine-rest task sub-resources that allows authenticated attackers with no permission grants to access task comments and attachments by calling singular read and delete endpoints that lack the authorization-filtered checks enforced on their corresponding list endpoints. Using only a known object ID, attackers can exploit TaskAttachmentResourceImpl and TaskCommentResourceImpl methods such as getAttachment, getAttachmentData, deleteAttachment, and getComment to read or download task attachments and comments and to permanently delete task attachments.
This SUSE Linux Enterprise Kernel update addresses multiple security vulnerabilities including issues in netfilter, KVM SVM, 9p client walk error handling, iSCSI target encoding, and libceph state weight decoding. The update fixes these flaws to enhance kernel security and stability.
This update for python311 fixes the following issues:
- CVE-2026-15310: memory exhaustion in zipfile in bzip2/LZMA/Zstandard decompression (bsc#1277111).
- CVE-2026-15806: urllib.request.HTTPPasswordMgr credentials for one URL scheme sent over another scheme (bsc#1276223).
- CVE-2026-17084: StringPrep algorithm considered Unicode codepoint attributes outside Unicode 3.2.0 (bsc#1276226).
- CVE-2026-19445: reassigned SNI callbacks with unreferenced SSLContext instances can cause use-after-free
(bsc#1283969).
- CVE-2026-19553: omitted server_hostname arguments in wrap_bio() can cause silent hostname verification bypasses
(bsc#1283826).
- CVE-2026-19672: tarfile extraction filter bypass allows creation of directories outside the destination (bsc#1276227).
- CVE-2026-82049: tarfile extraction filters mishandle archives containing a hard link to a symbolic link, allowing file
modification and content disclosure (bsc#1280459).
Changes for python311:
- Update to 3.11.17:
- Security
- gh-158446: Fix a crash or incorrect output that could occur
when formatting a float or complex with a precision close
to the platform's INT_MAX. PyOS_double_to_string() now
raises ValueError for any precision of that magnitude,
regardless of presentation type or value, as the format
string parsers already did for precisions above INT_MAX.
- gh-157190: Fixed a vulnerability in the tarfile data and
tar extraction filters where a crafted archive using a hard
link to a symbolic link could change the permissions and
modification time of a file outside the destination
directory, and expose its contents inside the extracted
tree. This addresses CVE 2026-82049. (bsc#1280459,
CVE-2026-82049)
- gh-156793: asyncio: loop.start_tls() and
loop.create_connection() now validate the server_hostname
argument if an ssl.SSLContext is passed with check_hostname
set to True, emitting DeprecationWarning if server_hostname
is missing. (This will raise ValueError in Python 3.13 and
later.) (bsc#1283826, CVE-2026-19553)
- gh-156793: ssl.SSLContext.wrap_bio() now validates its
server_side, server_hostname and session arguments similar
to ssl.SSLContext.wrap_socket(), but for backward
compatiblity reasons emits DeprecationWarning instead of
ValueError.
In particular, a context with check_hostname enabled and no
server_hostname passed to wrap_bio() now emits
DeprecationWarning to indicate the hostname wasn't
checked. (In Python 3.13 and later, this raises
ValueError.)
- gh-157265: In tarfile, when extracting a link falls back to
extracting a member of the archive, skip the member when
the filter function returns None when called with the
extracted member's name replaced with the link's.
- gh-157953: Update bundled libexpat to version 2.8.5.
- gh-156002: Bound the amount of data zipfile decompresses
per read for members compressed with bzip2, LZMA, or
Zstandard, matching the existing limit for deflate. A small
archive member could previously expand into an unbounded
allocation even when read in small chunks. (bsc#1277111,
CVE-2026-15310)
- gh-155999: Fix the tarfile tar and data extraction filters
creating directories outside the destination for members
whose name leaves the destination and returns to it, such
as ../evil/../dest/sub/file. The containment check used the
resolved path, but intermediate directories were created
from the name as given. (bsc#1276227, CVE-2026-19672)
- gh-156293: Fix a crash in ssl when an sni_callback switches
a connection to another SSLContext and the context that
carries the callback is no longer referenced by the
application. Servers that keep their sni_callback context
alive (the usual case when it wraps the listening socket or
is stored on the server object) were not affected. This
addresses CVE-2026-19445. (bsc#1283969, CVE-2026-19445)
- gh-155292: Change the stringprep module and encodings.idna
codec to not consider Unicode codepoint attributes beyond
those defined in RFC 3454. (bsc#1276226, CVE-2026-17084)
- gh-155694: Fix CVE-2026-15806 by scoping HTTPPasswordMgr
credentials to the URL scheme, preventing credentials
stored for an HTTPS URL from being used for a matching HTTP
URL, while URIs without a scheme continue to match any
scheme. (bsc#1276223, CVE-2026-15806)
- Library
- gh-156002: zipfile again reads members through a
third-party decompressor installed by monkey-patching the
private _get_decompressor() to return an object that only
implements old BZ2Decompressor API from Python 3.3. Note
that decompressors without needs_input and two-argument
decompress() are vulnerable to CVE 2026-15310.
- gh-156353: Fix configparser parsing when using whitespace
in delimiters.
- Build
- gh-155757: Set the --argv0 argument to wasmtime for WASI
builds so the test suite passes. Otherwise the calculated
paths to the stdlib for frozen modules is incorrect.
- CVE-2026-15310: bound zipfile decompression for
bzip2/LZMA (bsc#1277111, gh#python/cpython#156002)
Multiple vulnerabilities in Plex Media Server version 1.43.2 and earlier are actively exploited in the wild to achieve remote code execution. Attackers chain four CVEs to deploy the XMRig cryptominer and a proxy tool named myawesomeproxy. Exploitation attempts began on October 17, 2026, with malicious payloads downloaded from known IP addresses. The proxy software may enable threat actors to use residential IPs to access corporate VPNs and email systems. Public proof-of-concept exploit code is available via the plex2shell project. No official patch or remediation information is currently provided.
The Blaze Demo Importer WordPress plugin before 1.0.17 does not sanitize uploaded SVG files and registers the SVG MIME type for the WordPress media library unconditionally, allowing authenticated users with the Author role or higher to upload a crafted SVG that executes arbitrary JavaScript in the browser of any user who opens the file.
CVE-2026-98821 is a vulnerability in the Linux kernel related to polled direct I/O (DIO) operations with user integrity metadata. The flaw occurs because the kernel incorrectly handles the iocb->private pointer when metadata I/O is involved, leading to a general protection fault during polling. This issue has been fixed in Linux kernel version 6.17 and related commits.
A cross-site request forgery (CSRF) vulnerability exists in dyad-sh dyad versions up to 1.16.0 in the OAuth Callback Handler component. This flaw allows remote attackers to perform unauthorized actions by manipulating requests. The issue is resolved by upgrading to version 1.17.0-beta.1. The vulnerability has a medium severity rating with a CVSS score of 5.3.
CVE-2026-110031 is a privilege escalation vulnerability in the Salon Booking System WordPress plugin versions from 10.17 up to but not including 10.31.11. It allows users with the custom salon staff role to assign arbitrary capabilities to other accounts when editing a customer, enabling escalation to administrator privileges and full site takeover.
Coder versions before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contain a user enumeration vulnerability. This occurs because the userpassword.Compare() function substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticated attackers can exploit this by submitting logins with the password "hunter2" and distinguishing HTTP 403 from 401 responses to enumerate valid user accounts and reveal the authentication provider of SSO-only users.
Coder versions before 2.29.17, 2.32.7, 2.33.8, and 2.34.2 contain a stored HTML injection vulnerability. This occurs because the ApplicationName and LogoURL settings are rendered into HTML output without proper escaping. Attackers with Owner role privileges can inject malicious HTML that appears in the Coder dashboard and SMTP notification emails.
A URL associated with attacker activity was observed multiple times between 2026-10-17 and 2026-10-19. This URL was used as an out-of-band callback or command-and-control (C2) endpoint, employing the T1071 technique (Application Layer Protocol). The attacker infrastructure was located in the Netherlands. Security teams are advised to block and monitor this URL and search their proxy, web, and WAF logs for any requests to it.
The Post Export Import with Media WordPress plugin up to version 1.17.2 contains a directory traversal vulnerability via the 'theme_slug' parameter. This vulnerability allows authenticated users with administrator-level privileges or higher to access files outside the intended directory if the 'peiwm_enable_admin_download_buttons' feature is enabled. The vulnerability has a medium severity rating with a CVSS score of 4.9.
Umbraco CMS versions before 17.7.1 and 18.2.1 have a missing authorization vulnerability that allows unauthenticated clients to connect to certain backoffice SignalR hubs. This flaw permits attackers to complete the SignalR negotiate step and receive notifications disclosing content keys, including unpublished content, and revealing editorial activity timing.