CVE-2025-59405 is a high-severity vulnerability in the Flock Safety Peripheral Android application used on license plate readers and AI compute devices. The app contains a cleartext DataDog API key embedded in its codebase, which can be trivially extracted by decompiling the application binaries without any privileges or user interaction. This exposure allows attackers to access the DataDog monitoring service with the compromised OAuth secret, potentially leading to unauthorized data access or manipulation. Although no known exploits are currently reported in the wild, the vulnerability poses a significant confidentiality risk. European organizations using these devices could face data leakage or monitoring disruption. Mitigation requires removing the embedded secret from client-side code and implementing secure secret management practices. Countries with higher adoption of smart city and law enforcement technologies, such as Germany, France, and the UK, are more likely to be affected. The vulnerability has a CVSS score of 7.5, reflecting its high impact on confidentiality with no required privileges or user interaction.
CVE-2025-7063 is a critical vulnerability in the Polska Akademia Dostępności (PAD) CMS that allows unauthenticated remote attackers to upload files of any type due to a client-controlled permission check parameter. This unrestricted file upload can lead to remote code execution (RCE) on affected systems. The vulnerability affects all three PAD CMS templates (www, bip, ww+bip) and the product is end-of-life with no patches forthcoming. The CVSS 4.0 base score is 10.0, indicating a critical severity with network attack vector, no authentication or user interaction required, and high impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the risk is significant given the ease of exploitation and potential for full system compromise. European organizations using PAD CMS should urgently consider mitigation strategies including isolating affected systems, disabling file upload functionality, or migrating to alternative CMS platforms. Poland is the most likely affected country due to the product’s origin and usage, but other European countries using PAD CMS may also be at risk. Immediate action is recommended given the lack of vendor support and critical nature of this vulnerability.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to 22.0.1049 and Application prior to 20.0.2786 (VA and SaaS deployments) configure the SSH client within Docker instances with the following options: `UserKnownHostsFile=/dev/null`, `StrictHostKeyChecking=no`, and `ForwardAgent yes`. These settings disable verification of the remote host’s SSH key and automatically forward the developer’s SSH‑agent to any host that matches the configured wildcard patterns. As a result, an attacker who can reach a single compromised container can cause the container to connect to a malicious SSH server, capture the forwarded private keys, and use those keys for unrestricted lateral movement across the environment. This vulnerability has been identified by the vendor as: V-2024-027 — Insecure Secure Shell (SSH) Configuration.
SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to version 3.2, a timing attack vulnerability exists in the SCRAM Java implementation. The issue arises because Arrays.equals was used to compare secret values such as client proofs and server signatures. Since Arrays.equals performs a short-circuit comparison, the execution time varies depending on how many leading bytes match. This behavior could allow an attacker to perform a timing side-channel attack and potentially infer sensitive authentication material. All users relying on SCRAM authentication are impacted. This vulnerability has been patched in version 3.1 by replacing Arrays.equals with MessageDigest.isEqual, which ensures constant-time comparison.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 22.0.843 and Application prior to 20.0.1923 (macOS/Linux client deployments) contain an arbitrary file write vulnerability via the response file handling. When tasks produce output the service writes response data into files under /opt/PrinterInstallerClient/tmp/responses/ reusing the requested filename. The service follows symbolic links in the responses directory and writes as the service user (typically root), allowing a local, unprivileged user to cause the service to overwrite or create arbitrary files on the filesystem as root. This can be used to modify configuration files, replace or inject binaries or drivers, and otherwise achieve local privilege escalation and full system compromise. This vulnerability has been identified by the vendor as: V-2023-019 — Arbitrary File Write as Root.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 1.0.735 and Application versions prior to 20.0.1330 (macOS/Linux client deployments) contain a vulnerability in the local inter-process communication (IPC) mechanism. The software stores IPC request and response files inside /opt/PrinterInstallerClient/tmp with world-readable and world-writable permissions. Any local user can craft malicious request files that are processed by privileged daemons, leading to unauthorized actions being executed in other user sessions. This breaks user session isolation, potentially allowing local attackers to hijack sessions, perform unintended actions in the context of other users, and impact system integrity and availability. This vulnerability has been identified by the vendor as: V-2022-004 — Client Inter-process Security.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 25.1.102 and Application versions prior to 25.1.1413 (Windows client deployments) contain an insecure temporary-file handling vulnerability in the PrinterInstallerClient components. The software creates files as NT AUTHORITY\SYSTEM inside a directory under the control of the local user (C:\Users\%USER%\AppData\Local\Temp\). An attacker who can place symbolic links or otherwise influence filenames in that directory can cause the service to follow the link and write to arbitrary filesystem locations as SYSTEM. This allows a local, unprivileged user to overwrite or create files as SYSTEM, leading to local privilege escalation and the ability to modify configuration files, replace or inject binaries, or otherwise compromise confidentiality, integrity, and availability of the system. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.
Openfire is an XMPP server licensed under the Open Source Apache License. Openfire’s SASL EXTERNAL mechanism for client TLS authentication contains a vulnerability in how it extracts user identities from X.509 certificates. Instead of parsing the structured ASN.1 data, the code calls X509Certificate.getSubjectDN().getName() and applies a regex to look for CN=. This method produces a provider-dependent string that does not escape special characters. In SunJSSE (sun.security.x509.X500Name), for example, commas and equals signs inside attribute values are not escaped. As a result, a malicious certificate can embed CN= inside another attribute value (e.g. OU="CN=admin,"). The regex will incorrectly interpret this as a legitimate Common Name and extract admin. If SASL EXTERNAL is enabled and configured to map CNs to user accounts, this allows the attacker to impersonate another user. The fix is included in Openfire 5.0.2 and 5.1.0.
An information exposure vulnerability in the Palo Alto Networks User-ID Credential Agent (Windows-based) can expose the service account password under specific non-default configurations. This allows an unprivileged Domain User to escalate privileges by exploiting the account’s permissions. The impact varies by configuration:
* Minimally Privileged Accounts: Enable disruption of User-ID Credential Agent operations (e.g., uninstalling or disabling the agent service), weakening network security policies that leverage Credential Phishing Prevention https://docs.paloaltonetworks.com/advanced-url-filtering/administration/url-filtering-features/credential-phishing-prevention under a Domain Credential Filter https://docs.paloaltonetworks.com/advanced-url-filtering/administration/url-filtering-features/credential-phishing-prevention/methods-to-check-for-corporate-credential-submissions configuration.
* Elevated Accounts (Server Operator, Domain Join, Legacy Features): Permit increased impacts, including server control (e.g., shutdown/restart), domain manipulation (e.g., rogue computer objects), and network compromise via reconnaissance or client probing.
The LB-Link BL-CPE300M AX300 4G LTE Router firmware version BL-R8800_B10_ALK_SL_V01.01.02P42U14_06 does not implement proper session handling. After a user authenticates from a specific IP address, the router grants access to any other client using that same IP, without requiring credentials or verifying client identity. There are no session tokens, cookies, or unique identifiers in place. This flaw allows an attacker to obtain full administrative access simply by configuring their device to use the same IP address as a previously authenticated user. This results in a complete authentication bypass.
A ReDoS (Regular Expression Denial of Service) vulnerability (CVE-2024-49761) was identified in the puppet-agent component of Red Hat Satellite 6 client. Red Hat Satellite is a system management solution used to provision and configure systems without requiring public Internet access. This vulnerability could allow an attacker to cause a denial of service via crafted input triggering inefficient regular expression processing. Red Hat has released updated packages that fix this issue and advises users to upgrade to these patched versions.
Red Hat JBoss Core Services is a set of supplementary software for Red Hat JBoss middleware products. This software, such as Apache HTTP Server, is common to multiple JBoss middleware products and packaged under Red Hat JBoss Core Services, to allow for faster distribution of updates and for a more consistent update experience.
This release of Red Hat JBoss Core Services Apache HTTP Server 2.4.62 Service Pack 1 serves as a replacement for Red Hat JBoss Core Services Apache HTTP Server 2.4.62, and includes bug fixes and enhancements, which are documented in the Release Notes linked to in the References section.
Security Fix(es):
* httpd: HTTP Session Hijack via a TLS upgrade [jbcs-httpd-2.4] (CVE-2025-49812)
* httpd: access control bypass by trusted clients is possible using TLS 1.3 session resumption [jbcs-httpd-2.4] (CVE-2025-23048)
* httpd: insufficient escaping of user-supplied data in mod_ssl [jbcs-httpd-2.4] (CVE-2024-47252)
* httpd: untrusted input from a client causes an assertion to fail in the Apache mod_proxy_http2 module [jbcs-httpd-2.4] (CVE-2025-49630)
* jbcs-httpd24-mod_security: ModSecurity Has Possible DoS Vulnerability [jbcs-httpd-2.4] (CVE-2025-47947)
A Red Hat Security Bulletin which addresses further details about this flaw is available in the References section.
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
The RubyGems package 'service-catalog-client' version 0.7.0 has been identified as malicious. It executes one or more commands associated with malicious behavior, posing a security risk to users who install or use this package. There is no CVSS score available for this threat. No official patch or remediation guidance is provided at this time.
The turboscan-client RubyGems package version 99.99.99 has been identified as malicious by the OpenSSF Package Analysis project. This package executes one or more commands associated with malicious behavior, posing a security risk to users who install or run it. There is no CVSS score available for this threat, and no official patch or remediation guidance has been provided. No known exploits in the wild have been reported. Users should avoid using this specific package version to prevent potential compromise.
The RubyGems package 'turboghas-client' version 99.99.99 has been identified as malicious by the OpenSSF Package Analysis project. This package executes one or more commands associated with malicious behavior, posing a security risk to users who install or run it. There is no CVSS score available for this threat. No official patch or remediation guidance is provided, and no known exploits in the wild have been reported.
The RubyGems package 'blackbird-client' version 99.99.99 has been identified as malicious by the OpenSSF Package Analysis project. The package executes one or more commands associated with malicious behavior, indicating it is designed to perform harmful actions. There is no CVSS score available for this threat, and no known exploits in the wild have been reported. No official patch or remediation guidance is provided. Users should avoid using this specific version of the package.
The RubyGems package 'authnd-client' version 99.99.99 has been identified as malicious by the OpenSSF Package Analysis project. This package executes one or more commands associated with malicious behavior, indicating it is a threat to users who install it. No official patch or remediation guidance is provided, and no known exploits in the wild have been reported. The package is not a cloud service, and the vendor has not issued an advisory or fix at this time.
The RubyGems package 'aqueduct-client' version 1.3.3 has been identified as malicious by the OpenSSF Package Analysis project. This package executes one or more commands associated with malicious behavior, posing a security risk to users who install or use it. No official patch or remediation guidance is currently provided.
A vulnerability in the Virtual Keyboard Video Monitor (vKVM) connection handling of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker with low privileges to conduct a stored cross-site scripting (XSS) attack against a user of the interface.
This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected system. An attacker could exploit this vulnerability by injecting malicious code into a specific data field in the interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. To exploit this vulnerability, the attacker must have valid user credentials with privileges that allow for vKVM access on the affected device.
Note: The affected vKVM client is also included in Cisco UCS Manager.
A vulnerability in the Virtual Keyboard Video Monitor (vKVM) connection handling of Cisco Integrated Management Controller (IMC) could allow an unauthenticated, remote attacker to redirect a user to a malicious website.
This vulnerability is due to insufficient verification of vKVM endpoints. An attacker could exploit this vulnerability by persuading a user to click a crafted link. A successful exploit could allow the attacker to redirect a user to a malicious webpage and potentially capture user credentials.
Note: The affected vKVM client is also included in Cisco UCS Manager.