Overzicht van binnengekomen advisories.
2179 resultaten gevonden
The Total Donations plugin for WordPress contains a critical privilege escalation vulnerability affecting all versions up to and including 2.0.5. Unauthenticated attackers can exploit this flaw to elevate their privileges to administrator level without any prior authentication. The vulnerability has been assigned CVE-2026-78570 and is documented by both NVD/NIST and security researchers at Patchstack and Wordfence. No patch details are explicitly mentioned, but the affected version ceiling is 2.0.5. The ability for unauthenticated users to gain admin access makes this a high-severity issue for any WordPress site running the affected plugin. Site administrators should immediately assess their exposure and apply any available updates or mitigations.
Bekijk origineel advisory →CVE-2026-55540 affects PraisonAI, a multi-agent teams system, in versions prior to 4.6.51. The vulnerability exists in the is_path_within_directory() function, which uses os.path.abspath() instead of os.path.realpath() when enforcing workspace boundaries. This flaw allows a symlink placed inside the workspace to point to locations outside the workspace while still passing the boundary check. As a result, tools such as read_file can be abused to access arbitrary files on the filesystem outside the configured workspace. The vulnerability represents a path traversal/sandbox escape issue that could lead to unauthorized file disclosure. It is particularly relevant in multi-agent AI system contexts where workspace isolation is a security boundary. The issue was fixed in version 4.6.58 of PraisonAI. A patch commit and security advisory are publicly available on GitHub.
Bekijk origineel advisory →Ech0 versions before 4.7.3 contain a server-side request forgery (SSRF) vulnerability in the fetchPeerConnectInfo function. The function uses unvalidated HTTP requests instead of safe request methods with proper URL validation. Authenticated attackers can supply arbitrary URLs to exploit this vulnerability. The attack vector involves triggering connection health checks or peer connection operations. Exploitation allows access to internal services and cloud metadata endpoints. The vulnerability requires authentication, limiting the attack surface somewhat. Cloud environments are particularly at risk due to metadata endpoint exposure. A fix is available in version 4.7.3 and later. The issue has been documented in both GitHub Security Advisories and VulnCheck. Organizations using Ech0 in cloud or internal network environments should prioritize upgrading immediately.
Bekijk origineel advisory →CVE-2026-16286 describes an unrestricted file upload vulnerability in TRtek Technological Products' Software Repository Management application. The flaw allows attackers to upload files with dangerous types, enabling the deployment of a web shell to the affected web server. Successful exploitation grants an attacker remote code execution capabilities on the server. All versions of Software Repository Management prior to commit 2fb4acee are affected. The vulnerability is classified under CWE for unrestricted upload of files with dangerous types. The advisory was published by the Turkish cybersecurity authority (siberguvenlik.gov.tr). No workarounds are noted; patching to the fixed commit is the recommended remediation. The issue carries a high criticality rating due to the direct risk of server compromise.
Bekijk origineel advisory →Adobe Campaign Classic (ACC) is affected by a critical OS Command Injection vulnerability (CVE-2026-76197) classified as Improper Neutralization of Special Elements used in an OS Command. The vulnerability allows arbitrary code execution in the context of the current user. No user interaction is required for exploitation, making it particularly dangerous. The scope of the vulnerability is changed, indicating impact can extend beyond the vulnerable component. Adobe has published a security advisory (APSB26-134) to address this issue. The vulnerability carries a high criticality rating and poses significant risk to organizations using Adobe Campaign Classic.
Bekijk origineel advisory →CVE-2026-75497 describes a SQL injection vulnerability in Webkul QloApps, a hotel booking and management platform. The vulnerability exists because the application fails to validate request parameters before passing them to a database query. A remote attacker with administrative privileges can exploit this by sending a crafted SQL payload to the 'bo_query' parameter in the 'CustomerMessage.php' file. Successful exploitation could allow unauthorized access to or manipulation of the underlying database. The vulnerability has been patched in commit 123c97c, available via a GitHub pull request. References include the NVD advisory, CVE record, and a CISA CSAF advisory file. The attack requires authentication with administrative-level access, limiting the attack surface but not eliminating risk in compromised or insider-threat scenarios.
Bekijk origineel advisory →CVE-2026-80049 describes a critical authorization bypass vulnerability in Airbyte Platform through version 2.0.0. The flaw exists because the platform resolves workspace authorization decisions based on a caller-supplied field rather than the actual resource's owning workspace. AuthorizationServerHandler extracts identifiers from raw JSON request bodies into X-Airbyte-* headers, and AuthenticationHeaderResolver.resolveWorkspace prioritizes the caller-supplied X-Airbyte-Workspace-Id over resource-derived headers. Endpoints that only expect a resource identifier in the request body can be reached with an injected workspaceId field, causing permission checks to run against the attacker-nominated workspace. Since no post-authorization check compares the resource's owning workspace with the authorized workspace, any authenticated workspace member can read source and destination configurations, trigger or cancel syncs, and delete connections, sources, and destinations belonging to other workspaces. The exploit requires only valid membership in any workspace, making it broadly exploitable across multi-tenant deployments.
Bekijk origineel advisory →NLTK versions up to and including 3.9.4 contain an unsafe pickle deserialization vulnerability in the TransitionParser.parse() method located in nltk/parse/transitionparser.py. The method invokes pickle_load() with the default parameter restricted=False, routing deserialization through WarningUnpickler, which does not override find_class() and thus permits arbitrary class resolution. An attacker can craft a malicious model file containing pickle gadget chains that execute arbitrary Python code with the privileges of the application user upon loading. While NLTK provides a RestrictedUnpickler class designed for safe deserialization, it is not utilized in production code paths, leaving users exposed. The vulnerability enables remote or local code execution depending on how model files are sourced and loaded. The issue has been addressed and fixed in NLTK version 3.10.0. Users are strongly advised to upgrade immediately to mitigate the risk of arbitrary code execution.
Bekijk origineel advisory →CVE-2026-55099 affects the Python icalendar library versions 7.1.0 through 7.1.2, where the Component equality method performs O(2^n) recursive comparisons on nested subcomponents. An attacker can craft a sub-kilobyte .ics file with deeply nested BEGIN:VEVENT blocks to trigger exponential CPU consumption. The vulnerability is exploited when applications perform equality, inequality, membership, deduplication, or normalization comparisons on parsed calendar data. Affected endpoints include calendar sync, import, invite processing, and any comparison paths. Parsing alone does not trigger the issue, but equal nested subtrees cause worst-case behavior. A few hundred bytes are sufficient to pin a CPU core for minutes or indefinitely, resulting in denial of service. The issue has been patched in icalendar version 7.1.3.
Bekijk origineel advisory →CVE-2026-65093 is a high-severity vulnerability in NVIDIA OpenShell for Linux that allows an attacker to perform a sandbox escape. Successful exploitation can lead to arbitrary code execution, escalation of privileges, data tampering, and information disclosure. The vulnerability was published via the NVD (National Vulnerability Database) and tracked by NVIDIA's product security team. No specific exploit details or active exploitation in the wild are mentioned in the article. The vulnerability affects Linux-based deployments of NVIDIA OpenShell. Given the potential for privilege escalation and code execution, this is classified as a high-criticality issue. Users and administrators running NVIDIA OpenShell on Linux systems should monitor NVIDIA's security advisories for patches and mitigations.
Bekijk origineel advisory →A vulnerability was identified in Fdawgs node-poppler versions up to 9.1.2 and 10.0.1 affecting multiple PDF processing functions in src/index.js. The flaw resides in the Argument Injection Handler component, where manipulation of the file_path argument leads to argument injection. Affected functions include pdfInfo, pdfToText, pdfToCairo, pdfToPpm, pdfImages, pdfToHtml, pdfToPs, pdfFonts, pdfDetach, pdfAttach, pdfSeparate, and pdfUnite. The vulnerability can be exploited remotely, increasing its risk surface. A patch has been identified with commit hash db6e3f79d3beb20601be7e59669c39811ae3c330 on the project's GitHub repository. Users are strongly advised to apply the patch immediately to mitigate the risk of exploitation.
Bekijk origineel advisory →CVE-2026-56710 affects Grav Login plugin versions before 1.0.16, where the onApiUserListRowAction unlock handler fails to validate the privilege level of the target account. An attacker holding api.users.write permission can exploit this flaw to clear login lockout counters on admin.super accounts. This effectively strips brute-force protection from the highest-privilege accounts in a Grav CMS installation without requiring equivalent super-admin permissions. The vulnerability represents a privilege escalation/authorization bypass issue that could facilitate subsequent credential-based attacks against administrator accounts. It has been assigned a high criticality rating. Fixes are available in version 1.0.16 of the Grav Login plugin, and advisories have been published on GitHub and VulnCheck.
Bekijk origineel advisory →CVE-2026-63072 is a vulnerability in OpenSSL's CMS decryption logic where the key-unwrap output buffer is sized based on the reported unwrapped key size, but the AES-WRAP-PAD primitive can write 8 bytes beyond the allocation. An attacker can craft a CMS message by changing a single OID byte to trigger a deterministic 8-byte out-of-bounds heap write when the victim calls CMS_decrypt(). This results in heap corruption, typically causing a Denial of Service. The vulnerability is classified as CWE-787 (Out-of-bounds Write), requires no special configuration, and is reachable via the public API. No FIPS modules are affected as the CMS code resides outside the FIPS module boundary. The fix sizes the unwrap output buffer for the worst-case scenario to prevent out-of-bounds writes. Multiple OpenSSL commits have been issued to address the issue.
Bekijk origineel advisory →CVE-2026-45018 affects Chainlit, a Python framework for conversational AI applications, in versions 2.4.0rc0 through 2.12.0. When the MCP feature is enabled, the POST /mcp endpoint is exposed without authentication. The validate_mcp_command() function only checks the executable name but fails to validate arguments passed to StdioServerParameters. An attacker can exploit npx's -c argument to execute arbitrary shell commands with Chainlit process privileges. If allowed_executables is unset, the None default permits any executable, worsening the exposure. The vulnerability requires no authentication to exploit, making it accessible to unauthenticated remote attackers. The issue has been patched in version 2.12.0. Organizations running Chainlit with MCP enabled should upgrade immediately.
Bekijk origineel advisory →Ech0 versions through 4.5.6 contain an OAuth redirect URI validation vulnerability in the parseAndValidateClientRedirect function (internal/service/auth/auth.go). The validation logic only compares the scheme and host of the client-supplied redirect_uri against an admin-configured allowlist, ignoring path, query, and fragment components. The unvalidated redirect_uri is embedded into a signed state JWT at login time. An attacker can craft a redirect_uri with a matching host but an attacker-controlled path; after the OAuth exchange, the victim is redirected to that path with a one-time exchange code in the query string. If the code leaks via Referer headers, analytics, or an open redirect on the allowed host, the attacker can redeem it at the public POST /api/auth/exchange endpoint to obtain the victim's access and refresh tokens, effectively achieving account takeover. The vulnerability has been fixed in version 4.7.3.
Bekijk origineel advisory →A critical authentication bypass vulnerability was discovered in PraisonAI, a multi-agent teams system, prior to version 4.6.58. The vulnerability exists in the create_auth_middleware() function, which fails to properly enforce authentication when the PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET environment variables are not configured. As a result, an externally bound Recipe server can accept unauthenticated POST requests to /v1/recipes/run endpoints even when authentication is supposed to be enabled. This effectively renders the authentication mechanism non-functional under certain configuration conditions. The flaw could allow unauthorized users to execute recipes on exposed servers. The issue has been patched in PraisonAI version 4.6.58. Users are advised to upgrade immediately to mitigate the risk of unauthenticated access.
Bekijk origineel advisory →The Jawn theme for WordPress contains a critical Privilege Escalation vulnerability affecting all versions up to and including 1.4.2. Unauthenticated attackers can exploit this flaw to elevate their privileges to administrator level, posing a severe risk to affected WordPress installations. No authentication is required to exploit this vulnerability, making it particularly dangerous. The vulnerability has been documented by both Patchstack and Wordfence security researchers. WordPress site administrators using the Jawn theme should update to a patched version immediately. The CVE identifier assigned is CVE-2026-78477. The issue represents a significant access control failure within the theme's code. Sites running vulnerable versions are at risk of full administrative compromise.
Bekijk origineel advisory →NLTK versions prior to 3.10.3 contain a path sandbox bypass vulnerability affecting corpus-reader constructors. Attackers can supply arbitrary corpus root paths to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors, enabling unauthorized access to filesystem content and SQLite databases outside the pathsec sandbox boundary. The vulnerability allows reading of files outside the intended data root, posing a significant data exposure risk. The issue has been addressed in NLTK version 3.10.3. Advisories have been published on GitHub Security Advisories and VulnCheck. Users of affected versions should upgrade immediately to mitigate the risk of unauthorized file system access.
Bekijk origineel advisory →NLTK versions before 3.10.3 contain a vulnerability in the java() function that fails to validate JVM options passed via the per-call options parameter. This allows attackers to inject dangerous JVM flags such as -agentpath, -javaagent, or @argfile when interacting with Stanford wrapper classes. Successful exploitation can lead to arbitrary code execution on the affected system. The vulnerability is tracked as CVE-2026-79675 and has been assigned a high criticality rating. A fix is available in NLTK version 3.10.3 and later. Users of Stanford NLP wrapper classes within NLTK are particularly at risk. The issue was disclosed via GitHub Security Advisories and VulnCheck. Organizations using NLTK for natural language processing pipelines with Java-based Stanford tools should update immediately.
Bekijk origineel advisory →CVE-2026-55536 affects PraisonAI, a multi-agent teams system, in versions prior to 4.6.58. The vulnerability resides in the Browser Server's _handle_connection() function, which validates Chrome extension origins using Python's re.match() with an unanchored regular expression: chrome-extension://[a-z0-9]{32}. Because re.match() only matches from the start of the string without requiring a full match, extra trailing characters in the origin are not rejected, allowing the WebSocket connection to be accepted. This flaw enables attackers to send start_session commands and perform unauthorized browser automation. The vulnerability represents an improper input validation issue in the origin-checking logic. A fix was released in PraisonAI version 4.6.58, which addresses the regex anchoring problem. Users are advised to upgrade immediately to the patched version.
Bekijk origineel advisory →