Overview of incoming advisories.
2186 results found
The justhtml Python library before version 1.16.0 contains multiple HTML sanitization bypass vulnerabilities that can allow dangerous content such as scripts or styles to survive sanitization, potentially leading to cross-site scripting (XSS). The issues primarily affect advanced usage scenarios rather than the default sanitization path. Specific bypass vectors include: mutating or reusing sanitization policy objects weakening later sanitization; programmatic DOM input missing mixed-case tag names like ScRiPt or StYlE; crafted doctype names serializing into active markup; and custom policies preserving SVG or MathML allowing animation elements, external URL references in presentation attributes, or DOM trees mislabeled with namespace='html' to bypass foreign-content checks. The vulnerabilities are fixed in justhtml version 1.16.0. Users relying on custom or programmatic sanitization policies are most at risk.
View original advisory →CVE-2026-78136 affects chirpmyradio CHIRP before commit 39178db, allowing eval injection through crafted CSV data. The vulnerability exists in the _clean_tmode function within drivers/kenwood_itm.py. An attacker can exploit this by supplying malicious CSV data, potentially leading to arbitrary code execution. A proof-of-concept has been published on GitHub demonstrating code execution via a malicious image file. The fix is available in commit 39178dbfc4fece083ab9ed20286d6ae3a91a718e in the official CHIRP repository. CHIRP is an open-source tool used for programming amateur radios, making this vulnerability relevant to the ham radio community. Users should update to a version including the patch commit to mitigate the risk.
View original advisory →A critical security vulnerability has been identified in Tenda CH22 firmware version 1.0.0.1. The flaw resides in the function formeditFileName located in the file /goform/editFileName. An attacker can manipulate the argument editNameMit to perform command injection attacks. The vulnerability is remotely exploitable, requiring no physical access to the device. A public exploit has already been released, increasing the risk of active exploitation. The affected product is a networking device manufactured by Tenda. This vulnerability poses a significant risk to users who have not applied patches or mitigations. The public availability of the exploit makes prompt action critical for affected device owners.
View original advisory →justhtml versions before 1.15.0 contain multiple security vulnerabilities in URL sanitization helpers, HTML serialization, Markdown passthrough, and custom sanitization policies. Attackers can bypass sanitization to inject active HTML and JavaScript through various vectors including encoded javascript: URLs, backslash-based relative URLs, and markup-breaking element/attribute names. The Markdown passthrough feature (html_passthrough=True) allows raw </textarea> reintroduction, and custom policies may preserve dangerous tags like <style>, <meta http-equiv=refresh>, and <base href>. While the default sanitize=True configuration is largely unaffected, helper APIs, programmatic DOM construction, and custom policy pipelines are at risk. The vulnerability has been assigned CVE-2026-5388 and addressed in justhtml 1.15.0. Security advisories have been published on GitHub and VulnCheck.
View original advisory →CVE-2026-9769 affects the justhtml Python library through version 1.9.1, fixed in 1.10.0. The vulnerability involves uncontrolled recursion during HTML parsing via the JustHTML() constructor. TreeBuilder.finish() unconditionally calls _populate_selectedcontent(), which recursively traverses the DOM tree through _find_elements()/_find_element() without any depth limit. An attacker supplying crafted HTML with deeply nested elements (approximately 1000 nested div tags, ~11 KB) can exceed CPython's default recursion limit. This triggers an unhandled RecursionError that can abort parsing, fail requests, or terminate worker processes. The impact depends on the host application's exception handling behavior, making it a denial of service risk for applications that parse untrusted HTML input.
View original advisory →justhtml versions 1.11.0 and earlier contain a vulnerability in the to_markdown() function that fails to properly escape HTML-significant characters such as angle brackets in text nodes. This allows untrusted input that is safely handled by to_html() to be emitted as raw HTML in Markdown output. Affected sources include entity-decoded text and content from RCDATA/RAWTEXT-parsed elements like title, textarea, noscript, and plaintext. The flaw enables a sanitizer bypass where potentially malicious HTML, including script tags, can pass through unescaped. When the resulting Markdown is rendered by a downstream processor, it can lead to cross-site scripting (XSS) attacks. The vulnerability is fixed in version 1.12.0. Users are advised to upgrade immediately to mitigate the risk of XSS exploitation.
View original advisory →A vulnerability was identified in vas3k TaxHacker up to version 0.8.2 involving hard-coded credentials. The affected component is the JWT Secret Handler, specifically the envSchema.parse function in lib/config.ts. The vulnerability arises from the manipulation of the BETTER_AUTH_SECRET argument, which results in hard-coded credentials being used. The attack can be initiated remotely, making it a significant security risk. The project maintainer was notified via an issue report but has not yet responded or released a patch. Hard-coded credentials can allow attackers to bypass authentication mechanisms and gain unauthorized access to systems. The vulnerability is tracked under CVE-2026-78062 and has been reported on VulDB as well as GitHub.
View original advisory →NLTK versions prior to 3.9.4 contain an unbounded recursion vulnerability in the JSONTaggedDecoder.decode_obj() function. Attackers can exploit this flaw by supplying deeply nested JSON structures that exceed Python's recursion limit. This triggers an unhandled RecursionError that crashes the Python process, resulting in a denial of service condition. The vulnerability requires no authentication and can be triggered remotely by crafting malicious JSON payloads. The fix is available in NLTK version 3.9.4 and later. Users of affected versions should upgrade immediately to mitigate the risk of process crashes and service disruption.
View original advisory →NLTK versions prior to 3.10.0 contain a critical misconfiguration in pathsec.py where the ENFORCE flag defaults to False. This causes all security validation functions to emit warnings rather than raising exceptions, effectively disabling security controls unless manually enabled by the user. As a result, attackers can bypass path traversal protections and pickle deserialization safeguards. The vulnerability stems from an insecure default configuration that places the burden of security activation on end users. Exploitation could lead to arbitrary file read/write via path traversal or remote code execution via unsafe pickle deserialization. The issue is resolved in NLTK version 3.10.0, which corrects the default enforcement behavior.
View original advisory →The WPeMatico RSS Feed Fetcher plugin for WordPress contains a missing capability check on the wpematico_import_settings function. This vulnerability affects all versions up to and including 2.8.24. Authenticated attackers with subscriber-level access or above can exploit this flaw to modify arbitrary WordPress site options. The vulnerability can be leveraged to change the default registration role to administrator and enable open user registration. This effectively allows attackers to create administrator-level accounts and gain full control of the WordPress site. The vulnerability is classified as an unauthorized data modification issue leading to privilege escalation. A patch has been committed to the plugin repository addressing the missing capability check.
View original advisory →SiYuan versions prior to v3.7.4 contain an arbitrary file deletion vulnerability in the /api/search/removeTemplate API endpoint. The vulnerability arises from an unvalidated path parameter that is passed directly to Go's os.RemoveAll function. Authenticated admin attackers can exploit this by supplying absolute filesystem paths, enabling recursive deletion of any file or directory accessible by the kernel process. This effectively allows an attacker to delete critical system files or application data anywhere on the host filesystem. The vulnerability is classified as high severity due to the potential for irreversible data destruction. A fix has been issued in SiYuan v3.7.4. Security advisories have been published on GitHub and VulnCheck. The issue requires admin-level authentication, slightly limiting the attack surface but not eliminating the risk in environments with multiple admins or compromised credentials.
View original advisory →NLTK versions before 3.10.3 contain a critical remote code execution vulnerability in the AllowlistUnpickler component. The flaw exists because the pickler validates only the pickle module string but not the global name, allowing attackers to bypass allowlist restrictions via dotted name attribute traversal. This enables resolution of callables outside the allowlisted namespace. Attackers can exploit this by crafting malicious transition-parser models that execute arbitrary commands when loaded via TransitionParser.parse and allowlisted_pickle_load. The vulnerability is tracked as CVE-2026-71513 and has been patched in NLTK version 3.10.3. Users are strongly advised to upgrade immediately to mitigate the risk of arbitrary command execution through untrusted model files.
View original advisory →NLTK versions prior to 3.10.2 are vulnerable to a symlink-based sandbox bypass in the FramenetCorpusReader component. Attackers who can place symlinks inside the corpus subdirectory can bypass path validation guards because the validation only checks that filenames contain no path separators. When these symlinks are resolved by methods such as frame_by_name(), _lu_file(), or doc(), they can point to arbitrary XML files outside the intended corpus root directory. This allows unauthorized read access to sensitive files on the filesystem. The vulnerability requires the attacker to have write access to the corpus subdirectory to plant malicious symlinks. The fix is available in NLTK version 3.10.2 and later. Users are advised to upgrade immediately to mitigate the risk of arbitrary file read.
View original advisory →WWBN AVideo through commit 9c39d8c8 contains an authorization bypass vulnerability rooted in the getToken() function, which generates tokens without binding them to a specific user identity or intended purpose. The Gallery plugin endpoint (plugin/Gallery/view/sections.php) issues these valid tokens to unauthenticated visitors, creating a critical security gap. Attackers can obtain a token from the Gallery endpoint without any authentication and then reuse it to bypass authorization controls in other subsystems, such as view/hls.php. This allows unauthorized access to restricted video content that should require proper authentication. The vulnerability represents a flawed token issuance and validation design, effectively nullifying access controls across multiple subsystems. No user interaction is required beyond a simple unauthenticated request to the Gallery endpoint.
View original advisory →A command injection vulnerability has been identified in TRENDnet TEW-821DAP version 2.2.01b05. The vulnerability resides in the /cgi-bin/upload.cgi file within the ssi component, where manipulation of the filename argument allows for command injection. The attack can be initiated remotely without physical access to the device. A public exploit has been released, increasing the risk of active exploitation. The vulnerability affects an unknown function within the identified file. Given the remote exploitability and public exploit availability, this poses a significant risk to affected devices. TRENDnet TEW-821DAP is a wireless access point, making this vulnerability particularly concerning for network security. Users are advised to apply patches or mitigations as soon as they become available.
View original advisory →The Mailgun for WordPress plugin versions up to and including 2.2.0 is vulnerable to Server-Side Request Forgery (SSRF) via path traversal. The vulnerability exists in the add_list() function due to insufficient input validation of user-controlled array keys from $_POST['addresses'], which are only passed through sanitize_text_field() before use. Unauthenticated attackers can exploit this flaw to make authenticated POST requests to any Mailgun API endpoint using the WordPress site's stored API key. This can be leveraged to create inbound email-forwarding routes that intercept password reset emails. Successful exploitation can lead to full administrator account takeover. No authentication is required to exploit this vulnerability, making it particularly dangerous for any site running the affected plugin versions.
View original advisory →NLTK versions before 3.9.3 contain a vulnerability in the downloader module that fails to verify file integrity after downloading packages and before extraction. This flaw allows attackers to perform man-in-the-middle (MITM) attacks or DNS poisoning to inject malicious package contents. Because no validation occurs prior to extraction, the malicious content is processed without detection. The vulnerability poses a significant supply chain risk for any application or workflow relying on NLTK's package downloading functionality. Users are advised to upgrade to NLTK 3.9.3 or later to mitigate the risk. The issue is tracked as CVE-2026-63310 and has been acknowledged in a GitHub security advisory.
View original advisory →CVE-2026-62243 affects Netty (io.netty:netty-handler) versions 4.2.0.Final through 4.2.16.Final and versions through 4.1.136.Final. The vulnerability disables TLS hostname verification on the SslProvider.OPENSSL client path when a plain (non-extended) X509TrustManager is used and Unsafe-based trust-manager wrapping is unavailable, specifically in Java 25+ environments. This misconfiguration allows man-in-the-middle (MITM) attackers to present certificates issued for different hostnames that are accepted without validation. The flaw exposes applications using Netty's OpenSSL provider to certificate spoofing and interception of encrypted traffic. Fixed versions are 4.2.17.Final and 4.1.137.Final. Users are strongly advised to upgrade to the patched versions immediately. The vulnerability is particularly significant given Netty's widespread use as a foundational networking library in Java-based enterprise and cloud applications.
View original advisory →A vulnerability in strongSwan before version 6.0.7 involves mishandling of identity parsing and cloning. Specifically, parsed EAP-Identities that result in an empty but non-NULL encoding are not correctly cloned. This flaw triggers a double-free condition when the duplicate identities are destroyed. Double-free vulnerabilities can lead to memory corruption, potential crashes, or arbitrary code execution. The issue has been addressed in strongSwan version 6.0.7. Users are advised to upgrade to the patched version immediately. The vulnerability is tracked as CVE-2026-47895 and is considered high severity.
View original advisory →CVE-2026-68766 describes a vulnerability in hashcat where the application fails to restrict command-line options when parsing restore files. Attackers can craft malicious restore files that inject output-redirecting options such as --outfile and --potfile-path. This allows appending attacker-controlled content to arbitrary files on the system. The vulnerability can lead to code execution when attackers target shell startup files such as .bashrc or .profile. The flaw exists in hashcat's restore.c source file around lines 365-369. A fix was committed to the hashcat repository and is available in versions after v7.1.2. The issue was also tracked in hashcat's GitHub issue tracker as issue #4738. VulnCheck published an advisory detailing the attack vector and impact. This represents a significant security risk for systems where untrusted restore files could be introduced.
View original advisory →