CVE Vulnerability Catalog
Translated CVE descriptions from NVD NIST - in English
Browse vulnerabilities by packageCISA KEV catalog updated: (v2026.09.04)
Weekly CVE digest
One email a week with newly published vulnerabilities worth knowing about. No account needed.
This digest covers new vulnerabilities in general, not your servers. If you want to know which of them actually run in your infrastructure, that is what Secvalis does: it scans your machines and reports only what concerns them.
A vulnerability in BOSH allows a local attacker to steal Basic-auth credentials or redirect UAA token requests via MITM. The methods HttpRequestHelper#create_async_endpoint and #send_http_get_request_synchronous hard-code OpenSSL::SSL::VERIFY_NONE, enabling traffic interception between bosh-monitor and the BOSH director or UAA.
A network man-in-the-middle between nats-sync and the BOSH director can steal the director credentials (Basic auth header or UAA client secret) and can tamper with the VM list that is written into the NATS authorization file. Stolen credentials grant administrative director access. UsersSync#bosh_api_response_body builds a Net::HTTP client with verify_mode = OpenSSL::SSL::VERIFY_NONE for every director call (/info, /deployments, /deployments/<name>/vms). Affected versions: BOSH all versions prior to v282.1.9 (inclusive); fixed in v282.1.9 or later.
Weak Randomness / Insecure Cryptographic Primitive (CWE-338) in Get-RandomPassword in BOSH-Ecosystem / windows-utilities-release allows a network attacker to estimate VM boot time and reconstruct a small candidate list to recover the Administrator password.
In BOSH (all versions prior to v282.1.12), the PackagePersister.validate_tgz function builds a shell command with a package name from the release.MF file without escaping. The Sequel validation (VALID_ID) runs after the shell command, so an attacker can inject shell commands via metacharacters in the package name.
The SP Project & Document Manager plugin for WordPress up to version 4.71 lacks a capability check in the view_file function. Unauthenticated attackers can read file metadata and obtain download links for arbitrary files in project folders, which may contain sensitive information. The authorization gate uses a negated nonce check OR-chained with permission checks, allowing bypass of all controls.
A vulnerability was found in ealpha072 Student-Management-System in the admin/config.php file of the Administrative Backend component. The issue involves improper authentication, allowing remote attacks. The exploit is publicly available.
Active IQ OneCollect version 2.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
Active IQ Config Advisor version 6.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
Server-Side Request Forgery (SSRF) vulnerability in the RestTemplate.getForEntity function in RestTemplateUtil.java in crmeb_java 1.4. An attacker can remotely manipulate the URL argument in the base64 Qrcode endpoint, leading to unauthorized server requests.
Acronis DeviceLock DLP for Windows prior to build 9.0.15051.93227 is vulnerable to local privilege escalation via DLL hijacking.
Local privilege escalation due to DLL hijacking vulnerability. Affects Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227.
Local privilege escalation due to EXE hijacking vulnerability in Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227.
A vulnerability in Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227 allows local privilege escalation due to excessive permissions assigned to child processes.
Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL matching (25,020 hashes) and CIPA blocklist matching (12,352 hashes).
Securly Chrome Extension version 3.0.7 downloads config.json over HTTP and compiles server-provided patterns as JavaScript regular expressions via new RegExp() without complexity validation. An on-path attacker can inject patterns causing catastrophic backtracking, resulting in denial of service on all browsing.
Securly Chrome Extension version 3.0.7 uses EVP_BytesToKey with MD5 and a single iteration for AES encryption. MD5 has been broken since 2004 and a single iteration provides no key stretching, weakening the encryption.
Securly Chrome Extension version 3.0.7 dynamically registers content13.min.js as a content script not declared in manifest.json, bypassing Chrome Web Store static security review. It runs on all URLs, immediately hides all page content, creates a full-page overlay, pauses all videos, and only restores content when the service worker confirms the page passes filtering. If Securly's servers are unreachable, pages remain indefinitely hidden.
Version 3.0.7 of the Securly Chrome Extension exposes multiple publicly accessible endpoints that allow unauthenticated access to sensitive data. The exposed information consists of SHA-1 hashes obfuscated with a simple Caesar cipher that can be easily reversed.
Version 3.0.7 of the Securly Chrome Extension contains hardcoded, plaintext AES passphrases in securly.min.js. These keys decrypt crisis alert keyword data and intervention site data.
Securly Chrome Extension version 3.0.7 downloads JSON files containing crisis alert keywords and filtering rules over unencrypted HTTP via the Fetch API. Other endpoints in the same extension correctly fetch IWF and CIPA data over HTTPS, demonstrating an inconsistent TLS implementation.