10224 matches found
CVE-2026-26899
An issue was discovered in luci-app-https-dns-proxy on OpenWrt PR 15 2026-01-17. The setInitAction function in /usr/libexec/rpcd/luci.https-dns-proxy allows authenticated users to execute arbitrary shell commands via shell metacharacters in the name parameter...
CVE-2026-26899: Improper Neutralization of Special Elements used in an OS Command
An issue was discovered in luci-app-https-dns-proxy on OpenWrt PR 15 2026-01-17. The setInitAction function in /usr/libexec/rpcd/luci.https-dns-proxy allows authenticated users to execute arbitrary shell commands via shell metacharacters in the name parameter...
CVE-2026-26899
The luci-app-https-dns-proxy component in OpenWrt PR #15 (prior to 2026-01-17) is vulnerable to arbitrary command execution. The setInitAction function in /usr/libexec/rpcd/luci.https-dns-proxy fails to properly neutralize shell metacharacters in the name parameter, allowing authenticated users t...
EUVD-2026-67101
An issue was discovered in luci-app-https-dns-proxy on OpenWrt PR 15 2026-01-17. The setInitAction function in /usr/libexec/rpcd/luci.https-dns-proxy allows authenticated users to execute arbitrary shell commands via shell metacharacters in the name parameter...
PT-2026-82517
Name of the Vulnerable Software and Affected Versions luci-app-https-dns-proxy versions prior to 2026-01-17 Description Authenticated users can execute arbitrary shell commands due to improper handling of shell metacharacters in the name parameter within the setInitAction function located in...
CVE-2026-26899
An issue was discovered in luci-app-https-dns-proxy on OpenWrt PR 15 2026-01-17. The setInitAction function in /usr/libexec/rpcd/luci.https-dns-proxy allows authenticated users to execute arbitrary shell commands via shell metacharacters in the name parameter...
CVE-2026-26899
An issue was discovered in luci-app-https-dns-proxy on OpenWrt PR 15 2026-01-17. The setInitAction function in /usr/libexec/rpcd/luci.https-dns-proxy allows authenticated users to execute arbitrary shell commands via shell metacharacters in the name parameter...
Linux Distros Unpatched Vulnerability : CVE-2026-79779
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - rclone versions before v1.75.0 fail to reject transport downgrades in redirect handling, allowing Basic authorization and Cookie headers to be replayed over...
CVE-2026-79780
rclone before v1.75.0 fails to sanitize IBM IAM bearer tokens and SSE-C encryption keys during S3 redirect callbacks, allowing credentials to be preserved across scheme or host changes. Attackers observing network traffic from a trusted endpoint can capture reusable IBM IAM tokens on same-host...
CVE-2026-79782 rclone before 1.74.4 Security Token Disclosure via HTTPS to HTTP Redirect
rclone before 1.74.4 fails to strip the X-Amz-Security-Token header when an S3 redirect changes scheme from HTTPS to HTTP on the same host. Attackers can intercept plaintext HTTP traffic to capture AWS STS session tokens sent in request headers...
CVE-2026-79782
rclone before version 1.74.4 does not strip the X-Amz-Security-Token header when an S3 redirect changes the scheme from HTTPS to HTTP on the same host. An attacker positioned to intercept the resulting plaintext HTTP traffic can capture AWS STS session tokens transmitted in request headers, poten...
CVE-2026-79782 rclone before 1.74.4 Security Token Disclosure via HTTPS to HTTP Redirect
rclone before 1.74.4 fails to strip the X-Amz-Security-Token header when an S3 redirect changes scheme from HTTPS to HTTP on the same host. Attackers can intercept plaintext HTTP traffic to capture AWS STS session tokens sent in request headers...
CVE-2026-79779
rclone versions before v1.75.0 fail to reject transport downgrades in redirect handling, allowing Basic authorization and Cookie headers to be replayed over plaintext HTTP after same-host HTTPS-to-HTTP redirects. An on-path attacker observing the plaintext hop can capture and reuse credentials to...
libgit2: libgit2: Network attacker can intercept HTTPS connections via inverted IP SubjectAltName comparison
A flaw was found in libgit2, a C library for Git functionality. An inverted comparison in the OpenSSL backend's certificate verification logic, specifically when handling IP-literal hosts and certificate IP SubjectAltNames, allows a network attacker to intercept HTTPS connections. By presenting a...
Malicious code in digitalexp-style-module-l9 (npm)
Source: amazon-inspector 4c1b3e9059995d4d535c65fafd0105eea420510acb17ad9befbc99c18aa25df9 package.json declares both preinstall and postinstall as node beacon.js, so beacon.js runs automatically on every npm install. beacon.js reads os.hostname, os.userInfo.username, process.cwd, and the package...
CVE-2026-79780: Exposure of Sensitive Information to an Unauthorized Actor
rclone before v1.75.0 fails to sanitize IBM IAM bearer tokens and SSE-C encryption keys during S3 redirect callbacks, allowing credentials to be preserved across scheme or host changes. Attackers observing network traffic from a trusted endpoint can capture reusable IBM IAM tokens on same-host...
CVE-2026-53624
A flaw was found in the Fiber web framework's helmet middleware. This vulnerability occurs because the middleware incorrectly checks for the HTTPS protocol, preventing the Strict-Transport-Security HSTS response header from being set. This can allow an attacker to bypass security mechanisms,...
CVE-2026-53583
A flaw was found in libgit2, a C library for Git functionality. An inverted comparison in the OpenSSL backend's certificate verification logic, specifically when handling IP-literal hosts and certificate IP SubjectAltNames, allows a network attacker to intercept HTTPS connections. By presenting a...
CoreDNS DNS-over-HTTPS DoS
The vulnerability of the DNS-over-HTTPS DoH method used by the coredns DNS server is related to an uncontrolled resource consumption. Exploiting this vulnerability could allow a remote attacker to cause a service failure...
PT-2026-81991
Summary HTTPS RR data returned from the DoH server was not properly handled. Unverified APLN data which could contain arbitrary byte sequences was written directly to the log. It could also cause unnecessary memory usage. The single-byte response code was also written directly to the log...