A vulnerability in D-Bus allows an unprivileged local user to cause the dbus-daemon to abort when a privileged monitoring client is attached and a driver-originated broadcast message cannot be delivered. This occurs due to an assertion failure related to message serial numbers. The issue is fixed in version 1.14.8-4.oe2403sp4.
This advisory addresses critical security vulnerabilities in the Red Hat Enterprise Linux 8.8 kernel live patch module for kernel-4.18.0-477.107.1.el8_8. The patch fixes three vulnerabilities: CVE-2026-64534, CVE-2026-98432, and CVE-2026-99999, which involve kernel subsystems nvmet-tcp and ipv4. These issues relate to improper checks and memory handling that could lead to system instability or security breaches. The update is provided as kpatch modules that can be applied to running kernels without rebooting.
A vulnerability in the PGPainless library allows remote unauthenticated attackers to bypass the built-in maximum layer depth limit for compressed OpenPGP packets. By crafting messages with deeply nested compressed packet structures, attackers can cause unbounded recursive decompression leading to resource exhaustion, thread blocking, and potential application crashes due to out-of-memory conditions. This affects applications using the library's inline-detach and MessageInspector components for processing untrusted OpenPGP messages.
Three distinct cyberattack campaigns are targeting US trucking and logistics companies by impersonating trusted digital platforms used in routine operations. These campaigns use fake portals and phishing infrastructure to harvest credentials, personal data, and fuel card information, distribute malware including Node.js backdoors, and deploy remote access tools like MeshCentral and CastleRAT. They exploit common workflows such as carrier verification, broker onboarding, and freight booking to compromise operational systems and extract sensitive data like BitLocker recovery keys.
CVE-2026-63412 is a critical code injection vulnerability in the janephp library prior to version 7.12.0. The vulnerability arises because the Jane open-api-3 generator includes OpenAPI query parameter names verbatim as array keys in generated PHP docblocks. If a query parameter name contains a PHPDoc closing delimiter, it can prematurely terminate the comment and inject attacker-controlled PHP code into the class body, including an __construct method that executes upon client instantiation. Exploitation requires generating a client from a malicious OpenAPI document and then using the generated SDK, allowing arbitrary PHP code execution with the consuming application's privileges. This issue is fixed in version 7.12.0.
SharpIppNext is a .NET Standard library for building Internet Printing Protocol clients and servers. Prior to 4.1.0, server-side SharpIppNext implementations using SharpIppServer.ReceiveRequestAsync or SharpIppServer.ReceiveRawRequestAsync pass incoming data to IppProtocol.ReadIppRequestAsync in SharpIpp/Protocol/IppProtocol.cs, where ReadDocumentStream is enabled by default and the remaining document body is copied with CopyToAsync into a MemoryStream without a size limit. An unauthenticated remote client can send an arbitrarily large IPP document body, exhausting process memory and causing an out-of-memory failure or service termination. Client-only implementations using SharpIppClient are not affected. This issue is fixed in version 4.1.0.
cf-manager is an all-in-one dashboard for managing multiple Cloudflare accounts and services. Prior to 1.1.2, worker/src/routes/workers.ts uses bare fetch(url) calls to retrieve user-supplied URLs and deploys the returned content as a Worker script using stored Cloudflare credentials. The multipart and JSON branches of POST /api/:accountId/workers and POST /api/batch-deploy accept URLs without protocol, destination, redirect, content-type, or response-size validation. An attacker with deployment API access, or unauthenticated access when API_SECRET is not configured, can make cf-manager access internal resources or fetch attacker-controlled JavaScript and execute it in the victim Cloudflare Workers account. This issue is fixed in version 1.1.2.
Bazarr is a companion application to Sonarr and Radarr. Prior to 1.6.3-beta.11, the /api/subtitles/subtitles-info handler uses SubtitleNameContents.get() in subtitles_contents.py and reads the caller-supplied subtitlePath after checking only its subtitle extension; because the resolved path is not confined to files indexed by Bazarr, traversal can read files outside the media library. The /api/subtitles/subtitles handler in subtitles.py passes caller-supplied path and reference to sync and translation without per-path authorization, allowing an out-of-library reference file to be read and output to overwrite a file outside the media library. The authenticate decorator gates both endpoints when API authentication is enabled, while auth = None allows access without credentials. Both paths can affect only files that the Bazarr process can read or write. This issue is fixed in version 1.6.3-beta.11.
Oracle has addressed 71 vulnerabilities in Oracle E-Business Suite and related components, including 19 that can be exploited remotely without authentication. These vulnerabilities affect multiple Oracle products such as Oracle Applications Framework, Oracle Application Object Library, Oracle Universal Work Queue, Oracle Mobile Field Service, and Document Management and Collaboration. The fixes are part of Oracle's November 2026 Critical Security Patch Update, which includes 655 security patches across various Oracle product families.
The Smash Balloon Social Post Feed – Simple Social Feeds for WordPress plugin is vulnerable to stored cross-site scripting (XSS) via the 'attachments.data[].description' parameter in all versions up to and including 4.15.1. This vulnerability allows unauthenticated attackers to inject arbitrary scripts that execute in the browsers of visitors viewing pages with the affected shortcode. The flaw arises from insufficient input sanitization and output escaping of attachment descriptions contributed by outside Facebook users. No WordPress account is required to exploit this issue.
The Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.3.8. The vulnerability exists because the `new_customer_account()` function stores the raw return value of `wp_create_user()` — including a `WP_Error` object returned on username collision — into the order's `tp_userid` post meta before the `is_wp_error()` guard is evaluated; the `add_customer_details_to_thankyou_page()` callback subsequently reads that meta and casts it with `(int)`, causing PHP to coerce any object to integer `1`, after which `wp_set_current_user(1)` and `wp_set_auth_cookie(1)` are called unconditionally. This makes it possible for unauthenticated attackers to authenticate as WordPress user ID 1 — the bootstrap site administrator or, on multisite, a network super-admin — by supplying the `new_username` parameter matching any existing login during checkout and visiting the resulting thank-you page. Exploitation requires the Trust Payments gateway to be active and the attacker to complete a paid order on their own account; the ID 1 administrator username is additionally enumerable via standard WordPress user enumeration techniques.
A vulnerability in lldpd causes improper verification of LLDP-MED location record lengths, allowing an adjacent attacker to send crafted packets that trigger out-of-bounds reads in client applications using the liblldpctl library. This can lead to information disclosure of adjacent process memory. The flaw does not affect the lldpd daemon itself or remote networks beyond the local link. Exploitation is limited to local network attackers and requires use of custom applications consuming liblldpctl without length checks. No mitigation is currently available that meets Red Hat's criteria, and the lldpd service is optional and not enabled by default in Red Hat Enterprise Linux.
Supergateway versions 2.4.0 through 4.2.2 have a cross-site WebSocket hijacking vulnerability due to missing Origin header validation in stdio-to-WebSocket mode. This flaw allows malicious web pages to connect to the /message WebSocket endpoint from a victim's browser, including localhost-bound gateways, enabling attackers to initiate MCP sessions and invoke wrapped stdio MCP server tools with the victim's privileges.
The Heapless crate's `Deque::make_contiguous` function could incorrectly set internal state values, breaking invariants and causing out-of-bounds writes. This flaw affects versions prior to 0.9.4 and has been fixed in version 0.9.4.
Grav before 1.7.53.7 and 2.x before 2.2.18 contains an authentication bypass vulnerability that allows anonymous visitors to create super-admin accounts because UserCollection::count() uses an unescaped glob() pattern. On installs whose path contains brackets or a backslash, the account count returns zero, so attackers can send requests to POST /api/v1/auth/setup or the classic admin registration form to create or overwrite administrator accounts.
The Delivery & Pickup Date Time for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.3.90. This is due to a nonce-only settings AJAX handler that stores an attribute-breaking value and an administrator settings template that outputs it without HTML attribute escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.1.19 via comment content rendered on AMP post pages. The plugin registers an output-buffer callback ampforwp_the_content_filter_full() on the 'wp' action (priority 999) that applies a set of tag-agnostic and quote-agnostic regular expressions — notably /onclick=[^>]*/ — to the entire AMP page output after approved comments have already been echoed into it; these regexes do not understand HTML tag or attribute-value boundaries, so a kses-legal comment that places strings like 'onclick="' inside a title attribute value can trigger deletion of the title's closing quote, causing the browser to re-parse what was previously textual content inside the attribute value as live HTML attributes. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator has approved the comment.
The Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title (post_title)' parameter in all versions up to, and including, 3.0.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit is further enabled by wptexturize deliberately skipping texturization of content inside <code> elements and the default WordPress kses allow-list preserving <code> tags and raw double quotes on save, allowing a crafted title attribute breakout payload to survive storage and the the_title filter chain intact.
The Groundhogg plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_title' merge-tag of the [ghr] shortcode in versions up to, and including, 4.10 The post_title replacement is registered with 'nested' => true, so the nested branch of Replacements::do_replacement() returns the merge value through tackle_replacements() without passing it through escape_merge_tags()/escape_shortcodes(); the callback single_post() calls html_entity_decode(get_the_title(), ENT_QUOTES), converting the entity-encoded text that wp_filter_kses leaves intact on a Contributor's post title back into raw HTML, which is then emitted into the rendered post. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
The PowerPress Podcasting plugin by Blubrry plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 11.18.2 via the 'podcast-images[] (actually `${feed_slug}-images[]`)' parameter parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary image files on the server, which can contain sensitive information.