Overview of incoming advisories.
1553 results found
CVE-2026-59354 affects Spring Security's OAuth2 Authorization Server module versions 7.0.0 through 7.0.4. The vulnerability is triggered when Dynamic Client Registration is explicitly enabled, causing the registration endpoint to insufficiently validate client metadata fields. An attacker with a valid Initial Access Token can register a malicious client with crafted metadata. Depending on server configuration, this can lead to Stored XSS, Privilege Escalation, or Server-Side Request Forgery (SSRF). The CVSS v3.1 vector indicates network-accessible, low-complexity attack with low privileges required, no user interaction, and high impact on confidentiality and integrity with a changed scope. This makes it a high-severity vulnerability requiring prompt patching or mitigation.
View original advisory →A vulnerability has been identified in Spring MVC and WebFlux applications affecting Server-Sent Events (SSE) when used with view fragments. The flaw can lead to stream corruption, potentially impacting data integrity and application reliability. Affected versions include Spring Framework 7.0.0 through 7.0.8 and Spring Framework 6.2.0 through 6.2.19. The vulnerability is tracked as CVE-2026-47890 and has been published by NVD. Organizations using the affected Spring Framework versions should review their SSE implementations. The issue affects both the reactive (WebFlux) and traditional (MVC) web stacks within the Spring ecosystem. Patches or mitigations are expected to be available through official Spring security advisories. The criticality has been assessed as High given the breadth of affected versions and widespread use of the Spring Framework in enterprise applications.
View original advisory →CVE-2026-30056 is a NULL pointer dereference vulnerability found in the AMF NGAP Dispatcher component of free5gc version 4.0.1. Attackers can exploit this vulnerability by sending crafted NGAP messages during the initialization of a new RAN (Radio Access Network) connection. Successful exploitation results in a Denial of Service (DoS) condition, effectively crashing or disrupting the affected 5G core network component. The vulnerability is present in the open-source 5G core network implementation free5gc. This type of vulnerability is particularly significant given free5gc's use in research and production 5G network environments. The issue has been documented on the free5gc GitHub issue tracker.
View original advisory →ToolUniverse versions through 1.2.6 contain a critical vulnerability allowing unauthenticated remote code execution via a Python sandbox escape in the python_code_executor tool. The sandbox relied on a denylist approach that failed to block dunder attribute access through string lookups or permitted modules, enabling attackers to walk the class hierarchy to reach process and subprocess modules. Additionally, a per-call argument allowed callers to expand the import allow-list before inspection ran. The HTTP and MCP servers (http_api_server.py and smcp_server.py) bound to all network interfaces with debugging enabled and no authentication, meaning any network-reachable caller could execute arbitrary code as the server process. Version 1.3.0 mitigates these issues by adding bearer-token authentication, restricting the bind address to loopback by default, and hardening attribute inspection checks.
View original advisory →CVE-2026-81735 affects the mcp-http-server package in UI-TARS-desktop, where startServer.ts defaulted its listen address to '::' (all interfaces) when no host was specified. The authentication middleware was optional and never passed by the @agent-infra/mcp-server-commands and @agent-infra/mcp-server-filesystem entry points, leaving both servers completely unauthenticated. The commands server exposed a run_command tool that directly passed caller-supplied strings to child_process.exec, enabling unauthenticated remote code execution as the server process user. The filesystem server similarly exposed unrestricted file read and write capabilities. The fix changed the default listen address to 127.0.0.1 in commit c2ad42e3eb9b27830db41a3e6f51ca7179d9b168, but the package version remained at 1.2.4, making the commit the remediation boundary rather than a versioned release. Any network-accessible attacker could exploit this to fully compromise the host system.
View original advisory →CVE-2026-81525 affects the MongoDB client library for PHP, which fails to sufficiently sanitize special elements in application-supplied namespace identifiers. When untrusted text is incorporated into these identifiers, database operations may be silently redirected to unintended storage locations. This represents a namespace injection vulnerability that could lead to data integrity issues or unauthorized data access. The flaw exists in both the mongo-php-driver and mongo-php-library components. Patches have been released in mongo-php-driver version 1.21.7 and mongo-php-library version 2.4.1. Applications accepting user-supplied input for database or collection names are most at risk. The vulnerability could allow attackers to manipulate which database collections are targeted by application operations.
View original advisory →A heap buffer overflow vulnerability exists in rsyslog's RainerScript replace() function. An unauthenticated remote attacker can exploit this flaw by sending specially crafted syslog messages. The root cause is an incorrect buffer size calculation during string replacement operations, leading to memory corruption. Successful exploitation results in a denial of service (DoS) condition on the affected system. The vulnerability does not require authentication, making it particularly dangerous for internet-exposed syslog infrastructure. It has been reported via Red Hat's security advisory system and the rsyslog GitHub security advisories. A corresponding Bugzilla entry exists for tracking the fix. Organizations relying on rsyslog for log aggregation should prioritize patching this vulnerability promptly.
View original advisory →NLTK versions before 3.10.3 contain a filesystem containment bypass vulnerability affecting the Downloader.download and Downloader.incr_download methods. The flaw allows attackers with write access to a shared downloader directory to create hardlinks pointing to files outside the intended install root. During normal package extraction, these hardlinks cause files outside the install tree to be overwritten. This constitutes a path traversal/containment bypass that can lead to arbitrary file overwrite on the host system. The vulnerability is exploitable in shared or multi-user environments where the downloader directory is accessible to multiple users. It has been patched in NLTK version 3.10.3. Advisories have been published on GitHub Security Advisories and VulnCheck.
View original advisory →The Workeera WordPress plugin before version 1.0.6 contains a critical vulnerability allowing low-privileged users (subscriber role or higher) to delete arbitrary files on the server. The plugin fails to restrict which values can be written to a user's candidate profile and does not validate or sanitize the stored file path before deletion. This lack of input validation and access control enables attackers to exploit the file deletion functionality maliciously. The vulnerability could lead to significant damage including deletion of critical system files, configuration files, or other sensitive data. Users are advised to update to version 1.0.6 or later to remediate the issue.
View original advisory →CVE-2026-47884 is a critical vulnerability affecting multiple versions of the Spring Framework. The flaw exists in the use of XsltView within Spring MVC applications. If an application has a wildcard '/**' mapping that results in view rendering and the view name is not explicitly specified, an attacker can exploit this to perform Server-Side Request Forgery (SSRF) and Remote Code Execution (RCE). The vulnerability spans a wide range of Spring Framework versions including 5.2.x through 7.0.x. Affected versions include Spring Framework 7.0.0-7.0.8, 6.2.0-6.2.19, 6.1.0-6.1.28, 6.0.0-6.0.30, 5.3.0-5.3.49, and 5.2.25.RELEASE and earlier. Organizations using Spring MVC with XsltView and wildcard mappings should prioritize patching or mitigation immediately given the potential for full system compromise.
View original advisory →openssl_encrypt versions before 1.4.9 contain a vulnerability in the login and register_with_email functions that fail to validate server URLs, allowing unencrypted http:// URLs and unconfigured hosts. This exposes sensitive credentials including client_id, passwords, and JWTs in cleartext over the network. Attackers positioned on the network path can intercept these credentials through a man-in-the-middle style attack. Successful exploitation can lead to full keyserver account takeover. The vulnerability has been assigned CVE-2026-81691 and is rated high severity. Users should upgrade to version 1.4.9 or later to remediate the issue.
View original advisory →openssl-encrypt versions before 1.4.9 contain a vulnerability where file passwords are not properly redacted in debug output. When passwords are supplied via bundled short-option spellings (e.g., -apHunter2) or abbreviated long-option spellings (e.g., --passw), the sanitizer fails to recognize and redact them. The sanitizer only handled exact option names, --option=value forms, and tokens starting with -p, leaving these alternate spellings unredacted. As a result, cleartext passwords are written to stderr and may appear in terminal scrollback, merged 2>&1 output, CI job logs, or GUI persistent debug logs. Anyone with access to these outputs can recover the plaintext password. Users should upgrade to openssl-encrypt 1.4.9 or later to remediate this information disclosure vulnerability.
View original advisory →CVE-2026-47891 affects Spring WebFlux applications that use the Aalto XML processor for XML input parsing. The vulnerability stems from the application failing to correctly enforce the maxInMemorySize limit, which could allow attackers to cause excessive memory consumption. The issue spans a wide range of Spring Framework versions including 5.2.x through 7.0.x. Affected versions include Spring Framework 5.2.25.RELEASE and earlier, 5.3.0-5.3.49, 6.0.0-6.0.30, 6.1.0-6.1.28, 6.2.0-6.2.19, and 7.0.0-7.0.8. This vulnerability is classified as high severity and was published via NVD (nvd.nist.gov). Users are advised to review the Spring Security advisory and upgrade to patched versions.
View original advisory →Unitree G1 EDU firmware versions through 1.5.2 contain a critical unauthenticated remote code execution vulnerability tracked as CVE-2026-76639. The vulnerability is exploitable by network-adjacent attackers through a chain of three weaknesses: an unauthenticated WebRTC-to-DDS bridge on TCP port 9991, a static AES-128 key stored with world-readable permissions, and a path traversal flaw in the chat_go knowledge upload API. Attackers can leverage these weaknesses to publish DDS control messages that restart the bashrunner service, plant malicious payloads via path traversal, and trigger their execution as root (uid 0). The attack chain ultimately grants full root-level command execution on the affected robotic platform. This vulnerability poses significant risk to deployments of the Unitree G1 EDU robot in research or educational environments. Public proof-of-concept code and detailed technical write-ups are available, increasing exploitation likelihood.
View original advisory →openssl_encrypt versions before 1.4.9 contain a shell injection vulnerability in the info command's reconstructed CLI block. The vulnerability arises because untrusted metadata fields are interpolated without proper quoting. Attackers can craft malicious metadata values, such as a pepper_name field containing shell commands. These commands execute when a user copies the printed CLI block into a shell session. The vulnerability is classified as a shell injection issue and affects all versions prior to 1.4.9. Users are advised to upgrade to version 1.4.9 or later to remediate the risk. The issue is tracked as CVE-2026-81698 and has been reported via GitHub Security Advisories and VulnCheck.
View original advisory →CVE-2026-30050 is a Denial of Service vulnerability found in free5gc v4.1.0, an open-source 5G core network implementation. The flaw exists in the ModifyAMFEventSubscriptionProcedure function within the processor/event_exposure.go file. Attackers can exploit this vulnerability by sending a specially crafted PATCH request to trigger a DoS condition. The vulnerability was reported via the free5gc GitHub issue tracker. No authentication bypass or data exfiltration is described, but service availability is at risk. The affected component relates to AMF (Access and Mobility Management Function) event subscription handling, a critical part of 5G network signaling. This could impact telecommunications infrastructure relying on free5gc for 5G core services. A fix or patch status was not explicitly mentioned in the article.
View original advisory →A critical unauthenticated SQL injection vulnerability has been identified in the Beautiful Taxonomy Filters WordPress plugin, affecting versions 2.4.6 and earlier. The vulnerability allows unauthenticated attackers to perform SQL injection attacks, potentially exposing sensitive database information or enabling full database compromise. No authentication is required to exploit this flaw, significantly increasing the risk profile. The issue is tracked as CVE-2026-78288 and has been published on the National Vulnerability Database. A patch or updated version beyond 2.4.6 is recommended to remediate the vulnerability. The vulnerability has also been documented by Patchstack in their WordPress vulnerability database. Site administrators running the affected plugin should update immediately to mitigate risk.
View original advisory →The pip package openssl-encrypt (versions 1.4.8 and earlier) stores mTLS client private keys in cleartext within a world-readable SharedPreferences file (permissions 0644). This exposure occurs via the desktop GUI Settings screen when a combined certificate and private key PEM is entered. A local attacker with filesystem access can trivially read the private key, enabling potential impersonation or decryption of mTLS-protected communications. The vulnerability is classified as a sensitive data exposure / insecure storage issue. Version 1.4.9 addresses this by writing the PEM to a dedicated file with restricted permissions (0600), storing only the file path in SharedPreferences, and migrating or scrubbing any existing cleartext values. The fix represents a significant improvement in credential storage hygiene. The issue is tracked as CVE-2026-81683 and has been disclosed via GitHub Security Advisories and VulnCheck.
View original advisory →openssl_encrypt versions prior to 1.4.9 employ under-parameterized PBKDF2-HMAC-SHA256 key derivation, using only 100,000 iterations for PQC keyfile private key protection and a mere 10,000 iterations for dual-encryption file-password verification. These iteration counts are considered insufficient against modern GPU and ASIC-accelerated brute-force attacks. Attackers who gain access to keyfiles or encrypted files can perform offline password brute-forcing at high speed. The vulnerability affects the confidentiality of wrapped private keys and file encryption passwords. Users are advised to upgrade to version 1.4.9 or later, which presumably addresses these weak cryptographic parameters. The issue is tracked as CVE-2026-81718 and has been published by NVD, GitHub Security Advisories, and VulnCheck.
View original advisory →CVE-2026-81690 affects the openssl-encrypt pip package before version 1.4.9, exposing a symlink-following vulnerability in its verify-usb v2 added-file allowlist scan. The flaw arises because rglob() in CPython does not descend into symlinked directories, while O_NOFOLLOW only guards the final path component during hashing. An evil-maid attacker with physical access to a removable drive can replace a tool-tree directory with a symlink pointing to a copy containing byte-identical files plus a malicious __pycache__/*.pyc file. Since the planted file is never enumerated, the verify-usb check reports PASSED despite the tampering. When the victim subsequently runs the portable install, the planted bytecode is executed, achieving arbitrary code execution. Both the 1.4.x and 1.5.x lines are affected, and the issue is fixed in version 1.4.9.
View original advisory →