{"items":[{"id":1767,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#604762: Multiple vendors vulnerable to Unicode Normalization Collision on macOS (APFS)","summary":"Overview\n\nA mismatch between Apple File System (APFS) filesystem and path resolution for multiple applications allows attackers to bypass security exclusions using alternative Unicode spellings. By supplying an alternative Unicode spelling or case-folded variant (such as\nß\nversus\nss\n) that bypasses the application's file write checks, a local attacker can overwrite files wherever the process has write permissions, potentially leading to data corruption, configuration hijacking, or code execution. Multiple vendors have assigned CVEs and issued patches to address this flaw.\n\nDescription\n\nSeveral archive tools, packaging systems, and runtimes enforce exclusion filters using pathname comparisons that do not match the underlying filesystem's resolution behavior.\n\nBy using a byte-for-byte comparison (such as\nß\nversus\nss\n), rather than full case folding, a vulnerable application can be tricked into silently overwriting protected files. This vulnerability exposes backup tools, forensic workflows, and CI/CD pipelines to unauthorized file modification.\n\nThe CVEs assigned during coordination are as follows:\n\nCVE-2026-14978\n\nHashiCorp go-slug could allow an attacker with local filesystem access to bypass .terraformignore exclusions and cause sensitive files to be included in Terraform slug uploads due to improper handling of Unicode normalization during path matching.\n\nCVE-2026-49401\n\nDenos permission system enforces filesystem and execution restrictions by comparing the requested path against the path supplied to --deny-read, --deny-write, --deny-run, or --deny-ffi. On macOS, those comparison were performed using raw-byte pathname matching while the APFS filesystem treats different Unicode spellings of the same name as the same file.\n\nCVE-2026-45110\n\nLibarchive contains a file overwrite bypass and a directory exclusion bypass, which could allow an attacker to add a file, such as password\\u### to an archive. The Apple File System will treat the file as /etc/passwd and silently overwritten.\n\nThe fix is pending release.\n\nCVE-2026-59890\n\nsetuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. Prior to 83.0.0, FileList applied MANIFEST.in exclude, global-exclude, recursive-exclude, and prune directives by matching compiled glob patterns against on-disk file names without Unicode normalization, so on macOS APFS or HFS+ an NFD file name could bypass an NFC exclusion rule and be packed into a source distribution. This issue is fixed in version 83.0.0.\n\nVU#604762.8\n\nVU# 604762.8 is a general tracking for this type of flaw.\n\nMultiple vendors are vulnerable to an incomplete handling of Unicode path collisions. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS) the library fails to lock colliding paths (e.g., ß and ss), allowing them to be processed in parallel.\n\nImpact\n\nLocal attackers can bypass file exclusion filters or path locks during archive extraction to overwrite files anywhere the process has write permissions, potentially leading to data corruption, configuration hijacking, or code execution. This risk extends to supply chain workflows, where the failure to correctly exclude items can result in the inadvertent inclusion of sensitive files in distributed artifacts or the corruption of CI/CD build steps.\n\nSolution\n\nThe CERT/CC recommends updating affected softwares to the latest version.\n\nRemediation Guidance\n\nDevelopers should implement path validation that accounts for the underlying filesystem's normalization behavior rather than relying on byte-for-byte comparisons. Ensure that all security filters use path formats that match the resolution logic used by the operating system.\n\nAcknowledgements\n\nThanks to the reporter Tomas Illuminati, a Cyber Security Researcher & Threat Intelligence Analyst. This vulnerability note was written by Christopher Cullen. The CERT/CC and the reporter, Tomas Illuminati, would like to thank the maintainers of the various pro…","url":"https://kb.cert.org/vuls/id/604762","published_at":"2026-11-16T16:17:31Z","updated_at":"2026-11-17T17:12:49Z","fetched_at":"2026-11-21T19:15:15.897893Z","severity":"unknown","cvss_score":null,"epss":0.0053,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"apple","product":null,"vuln_id":"CVE-2026-14978","vuln_ids":["CVE-2026-14978","CVE-2026-45110","CVE-2026-49401","CVE-2026-59890"],"tags":[],"cluster_id":1470,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1767","html":"https://vulnwatch.ve1ve2.com/item/1767"}},{"id":1768,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#644655: TightVNC and UltraVNC Viewer contains a heap-based buffer overflow","summary":"Overview\n\nA heap-based buffer overflow exists in the Tight JPEG decoding component of the TightVNC Windows Viewer version 1.3.10 and affected UltraVNC Windows Viewers. An attacker controlling a malicious VNC server can trigger memory corruption by sending a specially crafted screen update. Successful exploitation can crash the viewer and may allow arbitrary code execution, although only denial of service conditions were demonstrated during testing.\n\nDescription\n\nTightVNC and UltraVNC provide remote desktop access using the Remote Framebuffer (RFB) protocol. Their viewer applications connect to VNC servers and decode screen updates for local display. Tight encoding supports JPEG compression of image data within these updates.\n\nThe Windows viewer function\nDecompressJpegRect()\nallocates a heap buffer using a hardcoded maximum row width of 8,192 pixels but converts JPEG pixel data using the server-supplied rectangle width without adequately checking that the output fits within the buffer. A malicious server can supply an oversized Tight JPEG rectangle that causes the conversion loop to write beyond the allocated memory. In an allocation demonstrated during testing, which included 256 bytes of padding, the out-of-bounds write began at a rectangle width of 8,257 pixels.\n\nExploitation requires a vulnerable viewer to establish a session with an attacker-controlled or compromised VNC server and process its crafted update. The server can advertise a sufficiently large framebuffer, so checking that the rectangle fits within the advertised framebuffer does not, by itself, prevent this overflow. Authentication or transport encryption does not prevent exploitation by a malicious server participating in the session.\n\nImpact\n\nAn attacker controlling a VNC server can corrupt heap memory in a connected vulnerable viewer, terminating the application and interrupting the remote desktop session. Memory corruption may also permit arbitrary code execution with the privileges of the user running the viewer, but only denial of service was confirmed during testing.\n\nSolution\n\nReview the Vendor Information section for product-specific patch information.\n\nAccording to UltraVNC’s release notes, the Tight JPEG heap overflow vulnerability was addressed in version 1.8.2.8. Users should upgrade to a current supported release containing that fix, such as version 1.8.3.1.\n\nUnfortunately, we were unable to reach TightVNC to coordinate a fix for the affected 1.3.10 Windows viewer. Users should replace affected viewers with a maintained version or an alternative solution that has been confirmed to address the vulnerability.\n\nUntil a corrected viewer is deployed, restrict connections to trusted VNC servers only. This reduces exposure but does not protect against a compromised trusted server.\n\nAcknowledgements\n\nThank you to re9rch for reporting this vulnerability. This document was written by Michael Bragg.","url":"https://kb.cert.org/vuls/id/644655","published_at":"2026-11-13T00:08:48Z","updated_at":"2026-11-13T00:08:48Z","fetched_at":"2026-11-21T19:15:15.897897Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"microsoft","product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1768","html":"https://vulnwatch.ve1ve2.com/item/1768"}},{"id":1769,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#580079: Arbitrary file read/write vulnerability in ImageMagick-based applications with default configuration","summary":"Overview\n\nMultiple arbitrary file read and write vulnerabilities have been identified in applications that use ImageMagick with insufficiently restrictive security policies. Collectively referred to as\nImageTragick2\n, these issues arise when ImageMagick processes attacker-controlled SVG or PostScript content using dangerous coders or delegates permitted by its default or application-supplied configuration. An attacker who can upload an image, or otherwise cause an application to process crafted image content, may be able to read or write files accessible to the ImageMagick process. In some deployments, these capabilities may be chained to achieve arbitrary code execution, compromising the confidentiality, integrity, and availability of the affected application and host.\n\nDescription\n\nImageMagick\nis a widely used open-source image-processing suite. Web and content-management applications, including Ruby on Rails, WordPress, MediaWiki, ownCloud Classic, and Redmine, may use ImageMagick for operations such as thumbnail generation, cropping, conversion, and transformation. ImageMagick is also commonly included in containerized AI image-processing pipelines. It may operate before inference to normalize or transform inputs, or after inference to convert and prepare generated output. In these environments, images may originate not only from direct uploads but also from URLs, automated agents, datasets, model outputs, or other upstream services.\n\nTwo vulnerability variants have been identified:\n\nCoder invocation through SVG (MSL injection)\n\nImageMagick's SVG processing can allow a crafted SVG\n\nelement to invoke a dangerous coder through its\nxlink:href\nvalue, for example, by referencing an\nMSL:\nresource. ImageMagick may then interpret the referenced content as a Magick Scripting Language (MSL) script. The script can invoke additional image readers and direct attacker-controlled image data to selected filesystem paths, enabling unauthorized file access. Exploitation depends on the internal SVG coder and the required dangerous coders being available to the ImageMagick process.\n\nGhostscript invocation through content detection\n\nImageMagick's content-based format detection may identify crafted input as PostScript and invoke Ghostscript, a separate interpreter used by ImageMagick to handle PostScript, EPS, and PDF, even when the filename or declared type suggests another format. Although Ghostscript is invoked with\n-dSAFER\n, the observed configuration permits file access within\n/tmp\n. A crafted PostScript file may therefore read or write data in that directory. This can affect applications that use shared temporary storage for uploaded files, processing artifacts, sessions, or other security-sensitive data.\n\nThese issues highlight an important aspect of ImageMagick's security model: Behavior that can be restricted through a custom security policy is treated as a configuration issue, not a vulnerability in ImageMagick itself. Applications and distributions are therefore responsible for deploying a policy appropriate to their threat model. Many integrations, however, process untrusted content without a sufficiently restrictive policy.\n\nImpact\n\nAn attacker who can cause an affected application to process crafted SVG or PostScript content may be able to read or write files in directory locations accessible to the ImageMagick process. In some cases, arbitrary code execution is possible when file access can be combined with writable executable content. AI-enabled services that utilize ImageMagick may face additional exposure because of untrusted image processing. In container deployments, writable host mounts, shared volumes, credentials, or inference artifacts can substantially increase the impact of a successful exploit.\n\nSolution\n\nConsult the\nVendor Information\nsection for product-specific updates and mitigations. Users of products that integrate ImageMagick, including Ruby on Rails, WordPress, MediaWiki, ownCloud Classic, and Redmine,…","url":"https://kb.cert.org/vuls/id/580079","published_at":"2026-11-12T18:12:09Z","updated_at":"2026-11-12T18:12:09Z","fetched_at":"2026-11-21T19:15:15.897899Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1769","html":"https://vulnwatch.ve1ve2.com/item/1769"}},{"id":1770,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#685399: PromZard context key code injection leads to remote code execution","summary":"Overview\n\nThe npm library\npromzard\n, versions 4.0.0 and earlier, is vulnerable to remote code execution due to direct string interpolation of context object keys, which allows unsanitized JavaScript code injection.\n\nDescription\n\npromzard\nis a\nNode.js\nlibrary designed to automate configuration workflows by evaluating template modules and generating data objects via interactive prompting. The library allows users to provide a context object\nctx\nto expose specific data to the template module.\n\npromzard\nbuilds an object by walking the template module for\nprompt()\nand asynchronous functions. The keys of\nctx\n, however, are treated as raw JavaScript source code instead of inert data. The implementation performs direct string interpolation of\nctx\nkeys, without validation or sanitization, into the parameter list of a function-expression source string that is then evaluated with\nvm.runInThisContext()\n. A key containing attacker-controlled JavaScript syntax can be executed during evaluation.\n\nImpact\n\nAn attacker capable of influencing the\nctx\nobject’s keys (e.g. via parsed configuration file, an HTTP request, or environment variables) can break out of the function parameter list and inject arbitrary JavaScript code. This results in remote code execution within the context of the Node.js process.\n\nSolution\n\nUnfortunately, the maintainers of\npromzard\ncould not be reached to coordinate the vulnerability. The CERT/CC recommends users ensure that any data used to populate\nctx\nis strictly validated, and that arbitrary keys should not be passed from untrusted sources.\n\nAcknowledgements\n\nThanks to Abdullah Hamdan for reporting this vulnerability. This document was written by Alex Lewis.","url":"https://kb.cert.org/vuls/id/685399","published_at":"2026-11-12T15:09:39Z","updated_at":"2026-11-12T15:09:39Z","fetched_at":"2026-11-21T19:15:15.897901Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1770","html":"https://vulnwatch.ve1ve2.com/item/1770"}},{"id":1771,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#944667: ComfyUI-Easy-Use contains unauthenticated path traversal vulnerability","summary":"Overview\n\nComfyUI-Easy-Use version 1.4.1 and earlier contains a vulnerability in its\nsave_preview()\nhandler that allows an unauthenticated attacker to overwrite an installed custom node’s Python file. An attacker who can reach the affected ComfyUI instance over the network can use the overwrite to execute arbitrary code when ComfyUI restarts.\n\nDescription\n\nComfyUI is a node-based interface for building generative AI workflows. ComfyUI-Easy-Use is an extension that adds custom nodes and workflow utilities.\n\nAn attacker can upload a Python file to ComfyUI’s input directory then use\nsave_preview()\nto copy that file over an installed custom node’s\n__init__.py\n. Upon restart, ComfyUI will import and execute the modified node. Remote exploitation requires a deployment that exposes the affected routes to the attacker without authentication.\n\nImpact\n\nAn unauthenticated attacker who can reach the affected routes can execute arbitrary Python code and operating system commands with the privileges of the ComfyUI process. The attacker can read or modify models, workflows, and other files accessible to the process and obtain credentials available in its environment. Exploitation requires no user interaction. The reporter confirmed the vulnerability in ComfyUI-Easy-Use version up to verion 1.4.1.\n\nSolution\n\nUnfortunately, the maintainer of ComfyUI-Easy-Use could not be reached to coordinate this vulnerability. To mitigate the vulnerability, remove the extension or restrict network access to ComfyUI to trusted users. The maintainer have released a fix in main as commit 8a0f2fc412.\n\nAcknowledgements\n\nThanks to Nguyen Huy Hoang for reporting this vulnerability. This document was written by Alex Lewis and Michael Bragg.","url":"https://kb.cert.org/vuls/id/944667","published_at":"2026-11-12T14:48:14Z","updated_at":"2026-11-12T15:20:05Z","fetched_at":"2026-11-21T19:15:15.897903Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1771","html":"https://vulnwatch.ve1ve2.com/item/1771"}},{"id":1772,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#188754: FrodoBots EarthRover Mini+ firmware contains multiple vulnerabilities","summary":"Overview\n\nMultiple vulnerabilities in the FrodoBots EarthRover Mini+ firmware (version 6.2.4_6.2.5_0.614.0) may allow remote code execution, unauthorized access to onboard sensors, disclosure of sensitive information, and full compromise of affected devices. Exploitation may enable an attacker to remotely control the rover, access audiovisual streams, or pivot into the user’s network.\n\nDescription\n\nThe FrodoBots EarthRover Mini+ is a compact, internet‑connected mobile robot used in educational and consumer environments. The device includes a camera, microphone, motor controllers, and multiple onboard services. Multiple vulnerabilities in the EarthRover Mini+ firmware (version 6.2.4_6.2.5_0.614.0) can allow remote code execution, unauthorized access to onboard sensors, exposure of sensitive data, and complete device compromise. An attacker could potentially take remote control of the rover, access its audio and video streams, or use it to gain a foothold in its network.\n\nCVE-2026-121685\n: The firmware contains several sets of hard-coded, fleet‑wide credentials, including BasicAuth credentials for an Agora token service, AWS IAM (Amazon Web Services Identity and Access Management) access keys, Amazon Web Services Internet of Things Message Queuing Telemetry Transport (AWS IoT MQTT) credentials, and a Slack incoming webhook URL. Agora Token Service is an open source server that generates secure, time‑limited authentication tokens for use with Agora.io’s RTC (Real‑Time Communication) and RTM (Real‑Time Messaging) services. A Slack incoming webhook URL is a unique endpoint that lets external systems send messages into a Slack channel without the need for a full Slack application. These are embedded directly in\nfrodobot.bin\nand are accessible through static analysis of the publicly downloadable firmware or from any device. Extraction requires no special privileges.\n\nCVE-2026-121686\n: Unauthenticated remote command execution is allowed via Message Queuing Telemetry Transport (MQTT). A firmware method accepts arbitrary shell commands delivered via Amazon Web Services Internet of Things Message Queuing Telemetry Transport (AWS IoT MQTT) messages and executes them as root. Access is gated only by shared Internet of Things (IoT) credentials, with no per‑device authentication, enabling remote code execution (RCE) as root across the fleet. The IoT credentials are hard-coded in the firmware as discussed in\nCVE-2026-121685\n.\n\nCVE-2026-121687\n: Several local interfaces are exposed without authentication. These services allow full local compromise of device functionality and provide access to sensitive information.\n\n* HTTP REST API on port 80 (motor control, telemetry/GPS/IMEI) contains endpoints that reveal the plaintext Wi‑Fi password, enable Wi‑Fi join functionality, diagnostic export services\n\n* Android Debug Bridge (ADB) root shell on port 5555\n\n* SSH on port 22\n\nCVE-2026-121688\n: The firmware contains an insecure STM32 update mechanism. STM32 is a family of 32-bit microcontrollers and is based primarily on Arm Cortex-M processor cores. They are widely used in embedded systems, IoT devices, industrial controls, robotics, automotive electronics, and consumer products. The STM32 motor‑controller firmware is fetched over unencrypted HTTP. Integrity is validated only via MD5, with the hash provided in the same unprotected response. No code‑signing mechanism is implemented, allowing firmware to be replaced with potentially malicious code.\n\nCVE-2026-121689\n: The firmware exposes sensitive credentials through multiple insecure mechanisms. The Wi‑Fi PSK is stored in plaintext in\nwpa_supplicant.conf\nand is disclosed through unauthenticated API endpoints and diagnostic exports. Additionally, unauthenticated ADB access allows retrieval of the\n/etc/shadow\nfile.\n\nCVE-2026-121690\n: The firmware executes code with unnecessary privileges. All processes run as root and the system lacks privilege separation. The compromise of any single service results in…","url":"https://kb.cert.org/vuls/id/188754","published_at":"2026-11-09T16:21:18Z","updated_at":"2026-11-09T16:21:17Z","fetched_at":"2026-11-21T19:15:15.897904Z","severity":"unknown","cvss_score":null,"epss":0.00905,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-121685","vuln_ids":["CVE-2026-121685","CVE-2026-121686","CVE-2026-121687","CVE-2026-121688","CVE-2026-121689","CVE-2026-121690"],"tags":[],"cluster_id":1474,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1772","html":"https://vulnwatch.ve1ve2.com/item/1772"}},{"id":1773,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#385711: PrestaShop debug mode configuration allows PHP code injection","summary":"Overview\n\nPrestaShop's back-office Performance > Debug mode functionality contains a PHP code injection vulnerability. An authenticated attacker with permission to modify debug-mode configuration can submit crafted cookie configuration values that are written into an executable PHP configuration file. Successful exploitation could allow arbitrary code execution with the privileges of the PHP process.\n\nDescription\n\nPrestaShop is an open-source e-commerce platform for creating and managing online stores. Its back-office Performance configuration includes a Debug mode for developers, which is enabled based on a specified cookie name and value.\n\nPrestaShop's debug-mode configuration code inserts the user-controlled values\ndebug_cookie_name\nand\ndebug_cookie_value\ninto a PHP expression without adequately escaping or sanitizing them for use in PHP source code. The application writes this expression into the PHP\ndefine()\nstatement in\nconfig/defines.inc.php\nor\nconfig/defines_custom.inc.php\n. A crafted value can terminate the intended string and introduce attacker-controlled PHP statements. The modified configuration file is loaded during application initialization, causing the injected code to execute on a subsequent request.\n\nExploitation requires an authenticated back-office account with permission to modify debug mode settings and a configuration file writable by the PHP process. Root or operating-system administrator privileges are not required. Cross-site request forgery (CSRF) protection helps prevent unauthorized requests made through another user's session, but does not prevent exploitation by an attacker controlling an account with the required permissions. Injected code executes with the privileges of the PHP process. Affected release versions remain to be confirmed.\n\nImpact\n\nAn authenticated attacker with the required configuration permissions could execute arbitrary PHP code in the security context of the PHP process. This could allow access to application secrets and customer data, modification or deletion of application files and database contents, and disruption of store operations. Operating-system command execution depends on the PHP configuration and available functions. The vulnerability does not independently grant root privileges.\n\nSolution\n\nPrestaShop version 9.2.1 addresses this vulnerability. Administrators should upgrade affected installations to version 9.2.1 or later.\n\nIf an immediate upgrade is not possible, allow only trusted administrators to modify Performance and Debug mode settings, and restrict network access to the back office. Where operationally feasible, prevent the PHP process from writing to config/defines.inc.php and config/defines_custom.inc.php. This may also prevent legitimate configuration changes.\n\nAcknowledgements\n\nThanks to Deflask13 for reporting this vulnerability. This document was written by Michael Bragg.","url":"https://kb.cert.org/vuls/id/385711","published_at":"2026-11-09T14:53:28Z","updated_at":"2026-11-11T17:27:47Z","fetched_at":"2026-11-21T19:15:15.897906Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1773","html":"https://vulnwatch.ve1ve2.com/item/1773"}},{"id":1774,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#124705: BaseChat – Audio Dating App, Android version 9.8.1, contains multiple vulnerabilities","summary":"Overview\n\nMultiple vulnerabilities have been identified in the Android application, BaseChat – Audio Dating App, version 9.8.1, which ultimately compromise the privacy of users’ personal data and activity.\n\nDescription\n\nBaseChat is an online dating platform built in Flutter and targeted toward users over 18. It facilitates anonymous, voice-first interaction between users. Three distinct vulnerabilities have been identified within the shipped Android application.\n\nVU#124705.1:\nThe application fails open when validating TLS server certificates for connections to its backend API host. The application allows any self-signed certificate to bypass standard TLS security checks.\n\nVU#124705.2:\nPaid user accounts are mapped to a third-party RevenueCat subscriber database using raw MSISDNs (phone numbers), which are a guessable public identifier. Because the RevenueCat Software Development Kit (SDK) includes a public API key within the application’s Android Package Kit (APK), an attacker can query the RevenueCat’s API using predictable identifiers to retrieve individual user metadata.\n\nVU#124705.3:\nThe application writes Personally Identifiable Information (PII) to Android system logs in its production build. During voice calls, the application logs the remote party’s MSISDN through unstripped debug statements, which allows an attacker to recovery phone numbers of callers who are intended to remain anonymous.\n\nImpact\n\nImpacts of successful exploitation vary by vulnerability.\n\nVU#124705.1:\nA network-positioned attacker can intercept and modify API communication, potentially leading to account takeover via session credential theft.\n\nVU#124705.2:\nAn attacker can locate the public RevenueCat SDK key and query the RevenueCat API using arbitrary phone numbers to retrieve associated user metadata, including activity and purchase history.\n\nVU#124705.3:\nThe personal data, or PII, of other users, intended to be anonymous, can be accessed through local system logs. The application’s backend sending other users’ MSISDNs to the client in any capacity presents a privacy violation.\n\nThese vulnerabilities have been confirmed against Basechat – Audio Dating App, Android version 9.8.1.\n\nSolution\n\nUnfortunately, Mobile Trading GmbH, the owners of BaseChat, could not be reached to coordinate this vulnerability.\n\nAcknowledgements\n\nThanks to Mahmoud Ali Khan for reporting these vulnerabilities. This document was written by Alex Lewis.","url":"https://kb.cert.org/vuls/id/124705","published_at":"2026-11-03T15:42:35Z","updated_at":"2026-11-20T15:42:38Z","fetched_at":"2026-11-21T19:15:15.897908Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"google","product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1774","html":"https://vulnwatch.ve1ve2.com/item/1774"}},{"id":1775,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#203719: INFINITT PACS System Manager contains multiple code execution vulnerabilities","summary":"Overview\n\nINFINITT PACS installations using System Manager versions 3.0.11.3 and 3.0.11.5 contain vulnerabilities that may allow an attacker to execute arbitrary code. INFINITT Healthcare has remediated the issues in System Manager versions 3.0.12.3 and 3.0.12.5.\n\nDescription\n\nINFINITT PACS is an enterprise web-based medical imaging platform that stores, retrieves, and displays patient scans.\n\nCVE-2026-16305\n\nAn improperly protected update manifest may allow a local attacker to execute commands with administrative privileges when an update is approved.\n\nSmartExecute.exe\nreads and runs commands from\nexeclist.txt\nafter an update. Because of insecure file permissions on\nexeclist.txt\n, a low-privileged attacker can modify the file before it is processed to add arbitrary malicious commands. After\nSmartUpdate.exe\nlaunches, it runs\nSmartExecute.exe\nand the user can be prompted by User Account Control (UAC), which can allow the malicious command to execute with administrative privileges.\n\nCVE-2026-16306\n\nAn unsafe command dispatch through the registered\nimodular://\nURI scheme may result in code execution.\n\nA vulnerability in\nIModular.exe\nallows an attacker to execute certain application functions by supplying a crafted\nimodular://\nlink. The application reads the\ncmd\nvalue from the link and executes the corresponding function without verifying that the command is permitted or safe. By convincing an end user to open a crafted\nimodular://\nlink, an attacker can cause\nIModular.exe\nto access attacker-controlled files or run specific programs from a local folder or network share. The link also accepts a\nurl\nparameter that causes\nIModular.exe\nto connect to an attacker-controlled SignalR endpoint, creating an unauthorized outbound connection.\n\nImpact\n\nSuccessful exploitation of CVE-2026-16305 may allow a local, low-privileged attacker to execute arbitrary commands with administrative privileges on the affected workstation. An attacker could then install or modify software, access protected files, disable security controls, or establish persistent access to the system.\n\nSuccessful exploitation of CVE-2026-16306 may allow a remote attacker to execute code with the privileges of the affected user, access or modify data available to that user, and use the compromised workstation as a foothold for further attacks. The vulnerability may allow unauthorized outbound communication with an attacker-controlled SignalR server, potentially exposing sensitive information or enabling additional malicious activity.\n\nSolution\n\nThere are no indications that these vulnerabilities have been exploited. INFINITT Healthcare recommends upgrading affected installations to one of the following fixed System Manager versions:\n\nSystem Manager 3.0.12.3\n\nSystem Manager 3.0.12.5\n\nOrganizations should apply the appropriate update as soon as operationally feasible.\n\nAcknowledgements\n\nThanks to Piotr Berlinski from CyberArms.io for identifying these vulnerabilities, and to INFINITT for quickly addressing the problems. This document was written by Michael Bragg.","url":"https://kb.cert.org/vuls/id/203719","published_at":"2026-11-02T15:38:19Z","updated_at":"2026-11-11T17:27:10Z","fetched_at":"2026-11-21T19:15:15.897910Z","severity":"unknown","cvss_score":null,"epss":0.00914,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-16305","vuln_ids":["CVE-2026-16305","CVE-2026-16306"],"tags":[],"cluster_id":1480,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1775","html":"https://vulnwatch.ve1ve2.com/item/1775"}},{"id":1776,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#701544: Retraction of mpc-lib hardened derivation fails to protect ancestor isolation","summary":"Overview\n\nFireblocks' mpc-lib library contains a cryptographic fail-open vulnerability in its BIP32 hardened derivation implementation in the case of a missing private parent key. This breaks the ancestor isolation property of hardened derivation, allowing an attacker with a compromised lower-level signer share to recover the higher-level share it was derived from.\n\nAfter reviewing the feedback from Fireblocks and further analysis of the case, we have determined that this does not constitute a valid vulnerability. Fireblocks clarified that mpc-lib's signing protocols use only non-hardened BIP32 derivation and that a hardened index is handled as a non-hardened one. Effective exploitation would require privileged access, at which point the attacker would already hold the master share, rendering the issue moot.\n\nDescription\n\nFireblocks is a digital-asset custody and wallet platform that secures the private keys behind cryptocurrency wallets for institutions and exchanges, using multi-party computation (MPC) so that no single machine ever holds a complete key.\n\nFireblocks’ key security pipeline contains two layers: MPC, which splits a single key into shares, and hardened derivation, which mathematically isolates each share from its key hierarchy. Normally, the derivation delta between parent and child keys is formed by hashing the private parent key, a derivation index, and associated metadata.\n\nVU#701544.1\n\nA fail-open vulnerability was identified within the BIP32 hardened derivation implementation which fails to reject operations where no parent secret is present. If a parent key is missing, the implementation substitutes the secret parent contribution with a null buffer. Because the buffer becomes a known constant, 0, the delta becomes computable, violating ancestor isolation.\n\nImpact\n\nAn attacker who compromises a single MPC party's descendant signer share, and who knows the associated chain code, can compute the public derivation delta and subtract it to recover that party's ancestor share, repeating the operation up the hierarchy to obtain that party's root share. The isolation between derivation levels is reduced to a publicly computable scalar, so a single leaf-level share compromise extends to that party's shares across the entire key hierarchy managed by the MPC cluster.\n\nThe primary MPC secret-sharing layer still prevents reconstruction of a full private key from a single compromised party's shares, so this flaw does not by itself yield a spendable key. Its significance is the elimination of a defense-in-depth layer: hardened derivation no longer provides post-compromise ancestor isolation, threshold-security assumptions degrade as compromise propagates across derivation levels over time, and the downgrade occurs silently with no error or log signal. In BIP32 deployments where the chain code is treated as public, the precondition of knowing the chain code is trivially met.\n\nSolution\n\nAt the time of writing, Fireblocks could not be reached to coordinate this vulnerability, and no vendor fix is available. Integrators can, however, reduce exposure with the following mitigations.\n\nTreat the chain code as secret. The attack is only available to a party that knows the chain code, because the derivation delta is computed as HMAC-SHA512(chaincode, ...). Chain codes should not be distributed in watch-only extended public keys or otherwise exposed to untrusted parties. Where a deployment can keep the chain code confidential, the delta is no longer publicly computable and ancestor-share recovery is not possible. This is the most effective mitigation available without a code change.\n\nDo not rely on hardened derivation for isolation between signer shares. Audit derivation paths for hardened segments and treat the compromise of any single share as potentially exposing that party's other shares across the derivation hierarchy.\n\nA complete fix requires a change in the library.\n\nAcknowledgements\n\nThanks to hodlturk for reporting this v…","url":"https://kb.cert.org/vuls/id/701544","published_at":"2026-10-26T22:45:54Z","updated_at":"2026-11-11T14:37:12Z","fetched_at":"2026-11-21T19:15:15.897911Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1776","html":"https://vulnwatch.ve1ve2.com/item/1776"}},{"id":1777,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#128947: COVESA vsomeip excessive memory allocation in reliable (TCP) endpoint buffer handling","summary":"Overview\n\nvsomeip, COVESA's open source implementation of the SOME/IP automotive communication middleware, contained a memory allocation vulnerability present in versions 3.7.3 and below. A vsomeip reliable (TCP) SOME/IP endpoint grows its receive buffer to an attacker-declared message size before validating that the declared bytes have actually been received, allowing a remote, unauthenticated peer to exhaust host memory and deny service. The issue was reported publicly as COVESA/vsomeip issue #1009 and fixed in release 3.7.4 (2026-07-06).\n\nDescription\n\nCVE-2026-91141\n\nvsomeip is a middleware implementation of the Scalable service-Oriented MiddlewarE over IP (SOME/IP) protocol, widely used for service-oriented communication between electronic control units (ECUs) in automotive and other embedded environments. A SOME/IP message begins with a 16-byte header that includes a 32-bit length field declaring the size of the message that follows.\n\nA vulnerability was discovered in the handling of this length field on reliable (TCP) endpoints. When a message arrives, vsomeip grows its receive buffer to the size declared in the length field in order to read the incoming message, before confirming that those bytes have actually been received. In the default configuration, no size limit is applied to reliable endpoints, so a peer can declare a message size of up to roughly 4 GB and cause the receiver to allocate that memory. Because a freshly accepted connection reaches this path on its first message, no valid service, credentials, or SOME/IP authentication are required to trigger the allocation. The client endpoint contains the same behavior, where a malicious or compromised server can attack a connecting client.\n\nDeployments that explicitly configure a reliable message-size limit are not affected.\n\nThis issue is publicly known. It was reported as COVESA/vsomeip issue #1009 (opened 2026-02-26) and fixed in release 3.7.4 (released 2026-07-06).\n\nImpact\n\nA remote, unauthenticated peer can force the host to allocate an attacker-chosen amount of memory, up to approximately 4 GB per connection, by sending a single short message on a normal TCP connection to any reachable reliable SOME/IP endpoint in the default configuration. On a memory-constrained node this can terminate the service outright: a service limited to 1.5 GB was OOM-killed by a single 16-byte message claiming a 3 GB payload. On a memory-rich host, the allocation for a single connection is released when the connection closes, so sustained memory exhaustion and denial of service follow from holding or repeating connections, each forcing its own allocation.\n\nSolution\n\nUpgrade to vsomeip 3.7.4 or later.\nThis issue is fixed in release 3.7.4 (released 2026-07-06). The fix replaces the unlimited compile-time default (\nMESSAGE_SIZE_UNLIMITED\n) with a bounded\nDEFAULT_MAX_MESSAGE_SIZE\nof 10 MiB, so reliable endpoints reject an oversized declared length before growing the receive buffer even when no limit is explicitly configured. The release also adds a regression test for an oversized length field. The issue and fix are tracked publicly in COVESA/vsomeip issue #1009.\n\nDeployments that cannot upgrade immediately should apply the following mitigations.\n\nDeployments can explicitly set\nmax-payload-size-reliable\n(or the equivalent per-service reliable message-size limit) to a value appropriate for the service. Endpoints with such a limit configured reject oversized declared lengths and are not affected by this issue. This is the most effective mitigation available without upgrading.\n\nBecause the vulnerability is reachable by any host that can open a TCP connection to a reliable SOME/IP endpoint, exposure should be minimized through network segmentation. Reliable endpoints should be confined to trusted, isolated in-vehicle or lab networks, and firewall or access-control rules should limit connectivity to known, authorized peers. SOME/IP endpoints should never be exposed to untrusted or externa…","url":"https://kb.cert.org/vuls/id/128947","published_at":"2026-10-26T19:07:02Z","updated_at":"2026-10-26T19:11:08Z","fetched_at":"2026-11-21T19:15:15.897913Z","severity":"high","cvss_score":7.5,"epss":0.00619,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-91141","vuln_ids":["CVE-2026-91141"],"tags":[],"cluster_id":1482,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1777","html":"https://vulnwatch.ve1ve2.com/item/1777"}},{"id":1778,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#763488: Memory corruption vulnerabilities in PHP","summary":"Overview\n\nTwo memory-related vulnerabilities have been identified in PHP versions prior to 8.2.35, 8.3.36, 8.4.27, and 8.5.12. An unauthenticated remote attacker with network access to PHP web services can exploit these vulnerabilities via specially crafted HTTP requests to potentially achieve arbitrary code execution.\n\nDescription\n\nPHP is a widely used open-source scripting language designed for web development and server-side applications. It powers millions of websites and web applications worldwide and can be deployed through a variety of server configurations, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed.\n\nCVE-2026-109618\n: A memory corruption vulnerability exists in the out-of-memory (OOM) handling mechanism of PHP versions prior to 8.2.35, 8.3.36, 8.4.27, and 8.5.12. The vulnerability occurs when an OOM condition interrupts request processing while internal request data is only partially initialized; subsequent cleanup routines may access the invalid memory, potentially causing memory corruption and enabling arbitrary code execution.\n\nCVE-2026-109619\n: A use-after-free vulnerability exists in the global state management of PHP versions prior to 8.2.35, 8.3.36, 8.4.27, and 8.5.12. The vulnerability occurs when a worker retains a reference to request-owned state after its backing memory has been freed. A subsequent request handled by the same worker can access this stale state before normal request initialization resets it, potentially causing memory corruption and enabling arbitrary code execution.\n\nImpact\n\nSuccessful exploitation of these vulnerabilities allows an unauthenticated attacker to remotely execute arbitrary code via specially crafted HTTP requests, compromising the confidentiality, integrity, and availability of the web service and underlying infrastructure. Apache mod_php deployments are at particularly high risk, as proof-of-concept exploitation has demonstrated that unauthenticated requests can trigger the attack before any application code executes.\n\nSolution\n\nRefer to the Vendor Information section below for newly patched versions of PHP that remediate these vulnerabilities. All PHP users are strongly encouraged to update immediately to PHP 8.2.35, 8.3.36, 8.4.27, or 8.5.12. Source downloads are available on the official PHP release page at php.net/downloads.\n\nLinux users are advised to check with their distribution vendor for updated packages, as many distributions received patches in advance. For PHP 8.1 and older versions that no longer receive official updates from the PHP project, contact your LTS vendor for backported fixes or upgrade to a supported version. The PHP security team has provided limited source backports for PHP 7.4, PHP 8.0, and PHP 8.1 to assist users building from source or without access to an LTS vendor.\n\nIf immediate patching is not feasible, the following temporary mitigation measures may reduce exposure to specific attack paths, though they do not provide complete protection. Because these vulnerabilities are closely related, mitigations for both CVEs should be applied:\n\nFor CVE-2026-109618 (OOM Corruption):\n\nSet\nmemory_limit=-1\nat an administrative level so it cannot be overridden by applications, for example via\nphp_admin_value\nin the FPM pool or Apache configuration.\n\nSet a low\npost_max_size\n(8M for applications without file uploads, 32M if uploads are necessary).\n\nKeep\nupload_max_filesize\nbelow\npost_max_size\n.\n\nEnforce limits at the web server or proxy level for decoded request-body size, input variable count, multipart part count, header count, and nesting depth.\n\nUse container or cgroup limits as an availability boundary with policies that kill only the affected worker. Notably,\nRLIMIT_AS\nor\nRLIMIT_DATA\nshould\nnot\nbe used to bound memory, as these cause\nmmap()\nto fail once the limit is reached, triggering the vulnerable code path rather than preventing it.\n\nFor CVE-2026-109619 (Stale Global State):\n\nSet\nsession.upload_progress.enabled=0\nin p…","url":"https://kb.cert.org/vuls/id/763488","published_at":"2026-10-22T22:23:51Z","updated_at":"2026-10-22T22:37:36Z","fetched_at":"2026-11-21T19:15:15.897914Z","severity":"critical","cvss_score":9.2,"epss":0.99999,"is_kev":true,"has_exploit":true,"kev_due_date":"2026-10-29","vendor":"php","product":"PHP","vuln_id":"CVE-2026-109618","vuln_ids":["CVE-2026-109618","CVE-2026-109619","GHSA-6WMF-4RV5-P3RP","GHSA-W8HW-W9FX-J79W"],"tags":[],"cluster_id":39,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1778","html":"https://vulnwatch.ve1ve2.com/item/1778"}},{"id":1779,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#645818: Xerj Console API authentication bypass leads to unauthorized credential minting","summary":"Overview\n\nAn authentication bypass vulnerability in the Xerj Console API allows sessions to bypass passkey-backed requirements during token issuance. By exploiting this flaw, an attacker with an existing valid token can create independent, persistent successor credentials directly through the console API. This allows the attacker to maintain access and potentially escalate privileges within the Xerj ecosystem, even if the initial token is revoked.\n\nDescription\n\nXerj is an open-source search and indexing engine tailored specifically for AI agents utilizing the Elasticsearch API, allowing AI models to query a structured index.\n\nThe vulnerability,\nCVE-2026-97406\n, stems from a flaw in how session states are authenticated and handled within the Xerj system architecture. According to the documented security contract, the issuance of new API tokens must be strictly authorized by a passkey-backed session. However, the Xerj implementation converts both standard browser sessions and API bearer tokens into the same generic\nAuthSession\nobject. The token creation handler then accepts this generalized principal without verifying whether the session was authenticated via a passkey.\n\nBecause of this architectural oversight, an attacker who obtains or intercepts a valid Xerj API token can directly invoke the token creation endpoint, allowing them to create independent successor credentials with the same access levels of the original token. Furthermore, the Xerj platform lacks hierarchical revocation logic; consequently, revoking a compromised parent token has no effect on any descendant tokens spawned from it.\n\nImpact\n\nExploiting this vulnerability allows an attacker to gain persistent, unauthorized access that completely bypasses multi-factor controls. The security risk escalates significantly if the compromised token belongs to a Xerj account owner. In this scenario, the newly created successor token retains full administrative authority. An attacker can use this persistent access to issue a new account invitation, redeem it in their own browser, and successfully enroll an entirely independent, attacker-controlled passkey. This grants the attacker permanent control over the Xerj instance and its sensitive data indices, rendering the revocation of the initial token completely ineffective.\n\nSolution\n\nThe vendor could not be reached to coordinate this vulnerability and an official patch has not been made available at the time of this writing. Users are advised to monitor the project's GitHub repository for updates and install the latest version of this library once a fix has been released.\n\nAcknowledgements\n\nThanks to the reporter, Shiran Guez, a Principal Application Security Architect.\n\nThis document was written by Laurie Tyzenhaus.","url":"https://kb.cert.org/vuls/id/645818","published_at":"2026-10-20T18:09:44Z","updated_at":"2026-10-27T14:47:36Z","fetched_at":"2026-11-21T19:15:15.897916Z","severity":"unknown","cvss_score":null,"epss":0.00531,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-97406","vuln_ids":["CVE-2026-97406"],"tags":[],"cluster_id":1483,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1779","html":"https://vulnwatch.ve1ve2.com/item/1779"}},{"id":1780,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#410595: Google BoringSSL Name Constraints bypass in SAN validation logic","summary":"Overview\n\nFive Name Constraints findings in BoringSSL (VU#410595.8–.12) describe cases where certificate names may not be constrained as intended. Records .8, .9, .10 and .12 concern the legacy crypto/x509 path; .11 concerns the newer pki path. Two have been fixed, one is accepted, one is disputed, and one was declined.\n\nDescription\n\nName Constraints limit the names a subordinate certificate authority may issue. The reports concern how BoringSSL applies those limits to certain SAN (Subject Alternative Name) forms. The records do not share one status, and they do not all affect the same validation path.\n\nVU#410595.8\n(\nFixed 2026-03-04\n): A wildcard DNS name may not be treated as covering a specifically excluded host.\n\nVU#410595.9\n(\nAccepted\n): A URI with a colon before\n@\nmay cause the wrong host to be used when matching URI constraints.\n\nVU#410595.10\n(\nDisputed\n): The finding concerns first-@ domain extraction in rfc822Name constraint matching. How consuming mail applications interpret the submitted multi-@ input, and whether that creates deployment exploitation, was not established.\n\nVU#410595.11\n(\nRejected\n): Trailing-dot handling in rfc822Name domains. The BoringSSL team declined this on 2026-02-28 as below its security threshold.\n\nVU#410595.12\n(\nFixed 2026-03-04\n): Trailing-dot DNS names were not always normalized on the legacy validation path.\n\nUsing BoringSSL in a product does not mean that product invokes an affected path or name form.\n\nImpact\n\nThese findings matter only where Name Constraints are enforced on an affected path, a trusted signature can be obtained over attacker-chosen SAN fields, and the accepted name is used for authorization. Mixed-library environments may accept or reject the same certificate differently. Presence of BoringSSL does not, by itself, mean that Chrome, Android, or other products are affected.\n\nSolution\n\nBoringSSL fixes land in the\nupstream repository\nand reach products through each product's own update process.\n\nVU#410595.8 and .12 were fixed in\ncommit 5774eca\non 2026-03-04.\n\nVU#410595.9 is accepted and under coordination.\n\nVU#410595.10 is disputed.\n\nVU#410595.11 was declined.\n\nCERT/CC is not coordinating BoringSSL fixes. For vendor status, contact the BoringSSL team through the\nGoogle Issue Tracker\n. Operators should confirm whether their deployment uses an affected path, apply available updates, and keep issued SANs well formed. A second validator helps only when it uses the same inputs and fails closed.\n\nAcknowledgements\n\nThanks to Oleh Konko for discovering and reporting these issues. This document was prepared with AI assistance by Timur Snoke.","url":"https://kb.cert.org/vuls/id/410595","published_at":"2026-10-14T15:11:33Z","updated_at":"2026-10-27T14:49:18Z","fetched_at":"2026-11-21T19:15:15.897934Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"google","product":null,"vuln_id":null,"vuln_ids":[],"tags":[],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1780","html":"https://vulnwatch.ve1ve2.com/item/1780"}},{"id":1781,"source":{"id":"certcc","name":"CERT/CC Vulnerability Notes"},"title":"VU#948176: Multiple TLS libraries can bypass delegation enforcement","summary":"Overview\n\nThis note covers thirteen library-specific records (VU#948176.6, .8–.19) of how widely used TLS libraries apply X.509 Name Constraints. The records describe cases where a constrained name may be accepted by one library and rejected by another. Some are fixed, some remain under review, and some were not accepted as security issues.\n\nDescription\n\nName Constraints are meant to keep a subordinate CA inside an allowed namespace. The records cover several name forms and do not all have the same classification. VU#948176.7 does not exist.\n\nDNS case-sensitivity and wildcards.\nWhile RFC 5280 requires case-insensitive DNS matching, it does not explicitly define wildcard Subject Alternative Name (SAN) matching, leading to varied implementation behaviors. For instance, GnuTLS was found to perform case-sensitive comparisons on certain names (CVE-2026-3833, fixed in 3.8.13). Similar discrepancies regarding case handling in wildcard parent-constraint lookups were reported in Go, as well as wildcard inconsistencies in LibreSSL and wolfSSL. Additionally, pyca/cryptography was identified to check DNS Name Constraints against certificate SANs but failed to validate them against the requested peer name (CVE-2026-34073, fixed in 46.0.6).\n\nIP addresses.\nSome libraries treat IPv4 and IPv4-mapped IPv6 forms as different when matching constraints. The Go security team determined that report did not meet its security bar; similar reports exist for Apple's Security.framework and Mozilla NSS and are included as comparative evidence.\n\nURIs.\nLibraries can differ on which host they extract from a URI SAN. OpenSSL merged\nPR #30319\nfor an\n@\nin the path, query, or fragment; a separate userinfo-colon report remains in triage. Related URI reports exist for Apple, NSS, and wolfSSL (CVE-2026-3547, fixed in 5.9.0). A well-formed single\n@\nis handled per RFC 3986 by most implementations.\n\nCommon Name fallback.\nAWS-LC was reported to apply DNS constraints inconsistently when a leaf has no SAN and uses a wildcard Common Name (CN). The AWS-LC wildcard CN issue and a separate Unicode CN issue have been fixed.\n\nNon-critical constraints.\nIn the reported Mbed TLS configuration, non-critical Name Constraints are not enforced. RFC 5280 requires conforming CAs to mark the extension critical, and the reviewed Mbed TLS 3.x configuration rejects unsupported critical extensions. The vendor treats adding support as a feature request; the reporter's concern remains disputed.\n\nImpact\n\nThese records matter only when an attacker can obtain a trusted signature over chosen certificate fields, reach an affected validation path, and the application uses the accepted identity for authorization. Validator disagreement alone is not exploitation. Effects, if any, are deployment-specific and may include acceptance of a name outside the intended namespace.\n\nSolution\n\nCERT/CC is coordinating remediation across the affected projects. The following summarizes available status; individual entries reflect different reporting and confirmation dates.\n\nGnuTLS\n— CVE-2026-3833 fixed in 3.8.13.\n\npyca/cryptography\n— CVE-2026-34073 fixed in 46.0.6.\n\nwolfSSL\n— CVE-2026-3547 fixed in 5.9.0. The wildcard was addressed in\nPR# 9991\n.\n\nGo's\ncrypto/x509\n— Two reports are in triage. The IPv4-mapped IPv6 report was not accepted as meeting the project's security bar.\n\nOpenSSL\n— PR #30319 was merged and, as confirmed on 10 September 2026, is present in all then-current publicly supported versions. The separate userinfo-colon report remains in triage.\n\nApple's\nSecurity.framework\n— Three reports submitted on 2026-03-16 remain in triage.\n\nMozilla NSS\n— IP-address report under coordination.\n\nLibreSSL\n— Wildcard report under coordination.\n\nAWS-LC\n— The wildcard-CN and Unicode-CN name-constraints issues are both fixed in AWS-LC v1.71.0 (released 2026-03-19); Rust bindings fixed in aws-lc-sys v0.39.0.\n\nMbed TLS\n— Non-critical Name Constraints are not enforced in the reported configuration. Marking the extension cri…","url":"https://kb.cert.org/vuls/id/948176","published_at":"2026-10-14T15:11:20Z","updated_at":"2026-10-27T17:01:54Z","fetched_at":"2026-11-21T19:15:15.897936Z","severity":"low","cvss_score":1.7,"epss":0.00565,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-3833","vuln_ids":["CVE-2026-34073","CVE-2026-3547","CVE-2026-3833","GHSA-M959-CC7F-WV43"],"tags":[],"cluster_id":1484,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1781","html":"https://vulnwatch.ve1ve2.com/item/1781"}}],"total":15,"has_more":false,"next_cursor":null,"limit":50,"page":1,"grouped":false,"filter":{"builds":"exclude","source":"certcc"}}