Two vulnerabilities affecting the Red Hat rhc client tool and daemon have been addressed. One is a denial of service caused by excessive resource consumption via a crafted certificate (CVE-2025-61729). The other is a memory exhaustion issue in query parameter parsing in the Go net/url package (CVE-2025-61726). These issues could impact system stability by exhausting resources. A security update is available for Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions to remediate these flaws.
Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.
A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products. Due to improper validation of client certificate–based authentication in certain default configurations, the affected components may permit unauthenticated requests even when mTLS is enabled. This condition occurs when relying on the default mTLS settings for System REST APIs or when the mTLS authenticator is enabled for SOAP services, causing these interfaces to accept requests without enforcing additional authentication.
Successful exploitation allows a malicious actor with network access to the affected endpoints to gain administrative privileges and perform unauthorized operations. The vulnerability is exploitable only when the impacted mTLS flows are enabled and accessible in a given deployment. Other certificate-based authentication mechanisms such as Mutual TLS OAuth client authentication and X.509 login flows are not affected, and APIs served through the API Gateway of WSO2 API Manager remain unaffected.
Active Directory (AD) domain join accounts, commonly used during system build processes, are frequently exposed and inherit over-privileged access control lists (ACLs). These excessive permissions enable attackers to exploit Local Administrator Password Solution (LAPS) disclosures, Resource-Based Constrained Delegation (RBCD), and other high-impact attacks. Even with Microsoft's recommended mitigations, residual risks remain due to replication lag and Active Directory Certificate Services (AD CS) interactions that can allow recovery of pre-reset machine secrets. Hardening requires layered controls including restricting machine account creation to privileged users, ensuring Domain Admins own computer objects, and applying deny Access Control Entries (ACEs) for sensitive attributes like ms-Mcs-AdmPwd and msDS-AllowedToActOnBehalfOfOtherIdentity. The threat is high severity due to the potential for privilege escalation and lateral movement within AD environments. Detection and mitigation require careful monitoring and tailored ACL configurations. European organizations relying heavily on AD infrastructure are at risk, especially those with complex domain join automation and build pipelines. Countries with large enterprise sectors and advanced IT infrastructure such as Germany, France, the UK, and the Netherlands are likely most affected. The threat is rated high severity due to the broad impact on confidentiality, integrity, and availability, ease of exploitation via exposed accounts, and the critical role of AD in enterprise security.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 22.0.1049 and Application versions prior to 20.0.2786 (VA and SaaS deployments) contain insecure defaults and code patterns that disable TLS/SSL certificate verification for communications to printers and internal microservices. In multiple places, the application sets libcurl/PHP transport options such that CURLOPT_SSL_VERIFYHOST and CURLOPT_SSL_VERIFYPEER are effectively disabled, and environment variables (for example API_*_VERIFYSSL=false) are used to turn off verification for gateway and microservice endpoints. As a result, the client accepts TLS connections without validating server certificates (and, in some cases, uses clear-text HTTP), permitting on-path attackers to perform man-in-the-middle (MitM) attacks. An attacker able to intercept network traffic between the product and printers or microservices can eavesdrop on and modify sensitive data (including print jobs, configuration, and authentication tokens), inject malicious payloads, or disrupt service. This vulnerability has been identified by the vendor as: V-2024-024 — Insecure Communication to Printers & Microservices.
A fraudulent Certificate Authority (CA) issued HTTPS certificates that are trusted by Network Security Services (NSS) using the Builtin Object Token. This security advisory from Red Hat addresses this issue by updating NSS to mark such certificates as untrusted. The update affects all uses of these certificates, including SSL, S/MIME, and code signing, but only for applications using the NSS Builtin Object Token. Applications using NSS but not the Builtin Object Token are not affected by this change. Users must upgrade NSS and restart affected applications for the update to take effect.