Nodemailer versions from 3.0.0 up to but not including 10.1.4 have a parsing flaw in the addressparser component. This flaw causes an RFC 5322 group to end prematurely at a semicolon inside quoted display names or comments. Attackers can exploit this by submitting crafted group addresses that pass validation but redirect emails to attacker-controlled recipients, bypassing recipient allow lists.
Red Hat OpenStack Platform 13.0 has multiple security vulnerabilities affecting components such as Nova, Keystone, and python-webob. These include arbitrary host file overwrite, resource allocation issues, privilege escalation, and an open redirect vulnerability. Red Hat has released updated packages to address these issues.
A phishing campaign impersonates OpenAI by sending fake ChatGPT Plus billing emails claiming failed subscription payments. Victims are directed to fraudulent payment pages hosted on compromised WordPress sites under Nexcess's nxcli.io infrastructure. Attackers monitor submitted credit card details in real time and dynamically request one-time passwords (OTPs) to complete fraudulent transactions. The campaign uses multiple redirect domains and identical client-side code across instances to steal credit card information and OTPs.
CVE-2024-2372 is an open redirection vulnerability where affected components accept user input for redirection URLs without proper validation. This flaw allows attackers to craft URLs that redirect users to arbitrary external domains, facilitating phishing attacks through social engineering.
A vulnerability in the follow-redirects library used in Red Hat Hardened Images RPMs (prometheus3.13) allows sensitive HTTP headers to be improperly forwarded during cross-origin redirects. This occurs because the sensitiveHeaders configuration is not correctly validated across different execution contexts, leading to potential disclosure of confidential authentication credentials to malicious redirect targets. Exploitation requires inducing HTTP requests to attacker-controlled hosts with specific configurations. The issue is rated as moderate severity and does not allow code execution or broader system compromise.
The NationalSecurityAgency/emissary package contains a vulnerability in its URL validation logic within NavAction.java. The regex intended to restrict URLs allows protocol-relative URLs (e.g., //evil.com) and single-slash scheme variants (e.g., http:/evil.com) to bypass validation. This flaw enables server-side request forgery (SSRF) and open redirect attacks. The vulnerability affects versions prior to 8.51.0, which includes the commit e2078417464b that introduced the flawed regex. The issue is rated medium severity with a CVSS score of 4.8.
CVE-2026-116250 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in pgAdmin 4 server mode before version 9.19. It arises when the application validates a user-supplied file path within the storage directory but subsequently opens the file without securely handling symbolic links or other special file types. This allows an attacker with write access to the storage backend to swap in symbolic links, hard links, or FIFOs to redirect file operations outside the intended directory, potentially leading to unauthorized file read, write, or execution as the pgAdmin OS user. The vulnerability was fixed in version 9.19 by securely opening files component-by-component with O_NOFOLLOW and passing open descriptors to utilities.
Hydra is a layer-two scalability solution for Cardano. Prior to 2.1.0, the `Claim` branch in `hydra-plutus/validators/deposit.ak` checks only that `datum.head_id` matches the attacker-controlled `redeemer.currencySymbol` and that the transaction is valid before the deposit deadline. It neither requires spending the Head state-token UTxO in the same transaction nor constrains outputs. After a deposit made through `POST /commit` is confirmed, any third party able to build a Cardano transaction can observe and consume the pending deposit UTxO before its deadline and redirect the assets to an arbitrary address. A standalone deposit spend invokes no Head validator, bypassing its safety checks; historical head-ID binding and the Aiken rewrite retained this missing invariant. The default deadline is three times depositPeriod, so the described attack applies to pending deposits before that deadline. This issue is fixed in version 2.1.0.
Business::GoCardless versions before 1.01 for Perl have a vulnerability where redirect flows are completed without verifying the session token. This allows an attacker who obtains another customer's redirect flow ID to create payments or subscriptions against that customer's mandate.
GitPython's Submodule.move() API does not properly validate symbolic links in the destination path, allowing an attacker-controlled symlink to redirect submodule moves outside the parent repository worktree. This can cause the submodule checkout to be moved to an unintended external directory, corrupting the parent repository's index and configuration. The vulnerability requires an attacker to supply a malicious Git repository with a symlinked path and the application to call Submodule.move() on a path beneath that symlink. No code execution or confidentiality impact is demonstrated, but the integrity of the repository is compromised.
Authlib versions from 0.13 through 1.7.2 contain a vulnerability in the is_secure_transport() function, which incorrectly treats certain HTTP URLs with a userinfo component as secure loopback addresses. This allows an attacker to bypass the TLS enforcement by crafting URLs like http://localhost:80@evil.example/cb, which are accepted as secure despite being cleartext HTTP to an external host. The flaw affects OAuth 2.0 / OIDC endpoint and redirect URI validation, potentially allowing cleartext non-loopback URLs to be accepted where TLS is required. The severity is low, and a fix is available in version 1.50.0.
The filelock ReadWriteLock and AsyncReadWriteLock components use SQLite databases for locking, but they pass SQLite a database name that SQLite reopens by following symlinks and acting on side files like -journal, -wal, and -shm. This behavior allows a local attacker with write permissions in the directory containing the lock database (if it is writable without the sticky bit) to plant symlinks or journal files that cause the lock user to overwrite or unlink files with their privileges. The vulnerability affects filelock versions 3.20.4 through 4.2.0, with the /proc/self/fd redirect introduced in 4.0.9 and side-file variants since 3.20.4. The issue requires local access and directory conditions that allow another user to create or rename files in the lock database directory. The CVSS 3.1 score is 7.1 (High) with high integrity and availability impacts but no confidentiality impact. A fix is available in version 4.7.0_1.