Overzicht van binnengekomen advisories.
2014 resultaten gevonden
GitPython versions before 3.1.59 contain a vulnerability where the library fails to disable merge_includes when parsing .gitmodules files. This allows attackers to craft malicious .gitmodules files containing [include] directives that point to arbitrary local files. When repo.submodules is accessed, GitConfigParser raises a MissingSectionHeaderError that embeds the first line of the targeted file verbatim in the exception message, causing unintended local file content disclosure. The vulnerability can be exploited to expose sensitive files on the host system. A fix is available by upgrading to GitPython 3.1.59 or later. The issue has been documented in both the GitHub Security Advisory and VulnCheck advisories. It is classified as a high-severity information disclosure vulnerability affecting applications that use GitPython to process potentially untrusted repositories.
Bekijk origineel advisory →CVE-2026-55532 affects PraisonAI, a multi-agent teams system, in versions prior to 4.6.58. The vulnerability exists in the MCP HTTP Stream _validate_origin function, which uses a startswith() check to validate request origins against an allowlist. An attacker can craft a malicious origin such as localhost.attacker.com that satisfies the localhost allowlist check due to the flawed string prefix matching. This allows cross-origin requests to be sent without CORS preflight by using Content-Type: text/plain, enabling unauthenticated access to the tools/call API endpoint without an API key. Successful exploitation can lead to unauthorized file writes that persist malicious agent instructions, potentially compromising the integrity of AI agent behavior. The vulnerability has been patched in PraisonAI version 4.6.58.
Bekijk origineel advisory →A heap out-of-bounds read vulnerability exists in OpenEXRUtil versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.12. The flaw is in the TypedDeepImageChannel<T>::row() API, which can return an out-of-bounds pointer when a deep image has a non-zero dataWindow origin. The root cause is a conflict between two coordinate models in ImfDeepImageChannel: at(x, y) uses absolute coordinates while row(r) is documented as 0-based logical access. For non-zero dataWindow.min values, row(0) points outside the _sampleListPointers allocation, causing a heap out-of-bounds read and potential crash. Under a controlled heap layout, this could lead to information disclosure. The vulnerability affects the EXR image format library widely used in the motion picture industry. Fixes are available in versions 3.3.13 and 3.4.13.
Bekijk origineel advisory →CVE-2026-55585 affects the QWED open-source AI verification package prior to version 5.1.2. The vulnerability stems from passing caller-controlled math expressions directly to SymPy's parse_expr() function without restricted namespaces, enabling arbitrary Python code execution via eval(). Two attack vectors exist: POST /verify/math and POST /verify/batch, both reachable with any valid tenant API key. The default-enabled signup endpoint allows anyone to self-register and obtain an API key, making the vulnerability unauthenticated in practice. Exploitation can lead to file read/write, OS command execution, service termination, and cross-tenant compromise in shared deployments. The issue is fixed in QWED version 5.1.2.
Bekijk origineel advisory →Grav CMS versions before 2.0.16 contain a symlink following vulnerability in the Scheduler Job::createLockFile() function. Local attackers can exploit this by pre-creating symlinks at predictable lock file paths within the world-writable temp directory. When a scheduled job runs, it follows the symlink and overwrites the target file with a job ID string. The attacker can point the symlink to any file writable by the web server process, enabling arbitrary file overwrite. This vulnerability requires local access but can have significant impact on system integrity. The issue has been patched in Grav CMS version 2.0.16. Multiple advisories have been published including on GitHub Security Advisories and VulnCheck.
Bekijk origineel advisory →Crater Invoice through version 6.0.6 contains a critical path traversal vulnerability in its self-update API. Authenticated company owners can exploit this flaw by supplying crafted ZIP archives containing ../ sequences to the unzip endpoint. The vulnerability stems from unsanitized ZIP entry names being passed directly to PHP's ZipArchive::extractTo() function. This allows attackers to write arbitrary files outside the intended extraction directory, including PHP files into web-accessible public directories. Successful exploitation results in remote code execution (RCE) on the server. The vulnerability requires authentication as a company owner, slightly limiting the attack surface but still posing a severe risk in multi-tenant or compromised credential scenarios. Public proof-of-concept and advisories are available, increasing exploitation risk.
Bekijk origineel advisory →A heap out-of-bounds write vulnerability exists in OpenEXR, the reference implementation for the EXR image format used widely in the motion picture industry. The flaw affects versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 on 32-bit/ILP32 builds. A specially crafted tiled EXR file with a small 40x40 dataWindow but an oversized 65537x65537 tile size can trigger the vulnerability through the TiledRgbaInputFile RGBA API. On ILP32 systems, the Array2D tile-conversion buffer size calculation overflows, causing allocation of a much smaller heap buffer than required. Tile decode operations then write past the allocated buffer boundary, resulting in heap memory corruption. The vulnerability has been patched in versions 3.2.11, 3.3.13, and 3.4.14. Exploitation requires an attacker to supply a maliciously crafted EXR file to a vulnerable application running on a 32-bit/ILP32 platform.
Bekijk origineel advisory →CVE-2026-79664 affects Ech0 versions before 4.7.3, where access tokens created with the never-expire option cannot be properly revoked. Three separate revocation mechanisms all fail: the logout function panics on a nil ExpiresAt field, RevokeToken skips revocation when remainTTL is zero, and the admin delete function does not blacklist the JWT ID (JTI). As a result, stolen tokens remain cryptographically valid indefinitely unless the JWT secret is rotated. This allows attackers who obtain a never-expire token to maintain persistent authenticated access to the system. The vulnerability is classified as high severity due to the potential for perpetual unauthorized access. A fix is available in Ech0 version 4.7.3 and later.
Bekijk origineel advisory →CVE-2026-24262 is a vulnerability discovered in the system firmware of NVIDIA DGX Spark. A privileged attacker can exploit an out-of-bounds write flaw in the firmware. Successful exploitation may result in arbitrary code execution, privilege escalation, denial of service, information disclosure, and data tampering. The vulnerability requires privileged access to exploit, somewhat limiting the attack surface. NVIDIA has published a security advisory through their product-security GitHub repository. The vulnerability is tracked by both NVD and CVE.org. Given the range of potential impacts including code execution and privilege escalation, this is considered a high-severity issue. The DGX Spark is an AI computing platform, making this vulnerability particularly relevant to high-performance AI infrastructure environments.
Bekijk origineel advisory →The getgrav/grav-plugin-login Composer plugin before version 3.9.1 contains a timing side-channel vulnerability in its password reset and account activation token comparison logic. The affected code uses a non-constant-time === string comparison instead of the secure hash_equals() function in classes/Controller.php and login.php. Additionally, the token submission endpoint (taskReset) lacks rate limiting, compounding the risk. An attacker with knowledge of a valid username could theoretically send repeated token guesses and use timing differences to recover a valid reset or activation token. The vendor acknowledges the flaw but rates practical exploitability as low, and no end-to-end network exploit has been publicly demonstrated. The fix is available in version 3.9.1 of the plugin.
Bekijk origineel advisory →PraisonAI, a multi-agent teams system, contains a critical vulnerability in its Jobs API where the create_app function mounts the /api/v1/runs endpoint without any authentication. Prior to version 4.6.51, any reachable caller could exploit this to submit jobs, read results, cancel runs, or delete jobs using operator-level credentials. This effectively grants unauthorized users full control over job operations without requiring any credentials. The vulnerability poses significant risk as it allows unauthenticated access to sensitive job management functionality. The fix introduces PRAISONAI_JOBS_API_KEY middleware that enforces authentication via Authorization or X-API-Key headers. The issue has been patched in version 4.6.58 of PraisonAI.
Bekijk origineel advisory →NVIDIA NemoClaw for Linux contains a critical vulnerability in its status and logs plugin commands that allows OS command injection. An attacker exploiting this flaw could achieve arbitrary code execution on the affected system. The vulnerability also enables data tampering, information disclosure, and denial of service attacks. The issue resides specifically in plugin command handling within the NemoClaw application. NVIDIA has published a security advisory referencing this CVE. The vulnerability has been assigned a high criticality rating given the potential for full system compromise.
Bekijk origineel advisory →CVE-2026-55528 affects PraisonAI, a multi-agent teams system, in versions prior to praisonaiagents 1.6.58. The vulnerability exists because AgentServer exposes ServerConfig.auth_token but the _create_app method fails to enforce authentication checks on any route. This allows remote unauthenticated callers to subscribe, publish, and perform other sensitive actions without providing a valid bearer token or X-Auth-Token header, even when authentication is explicitly configured. The flaw represents a complete authentication bypass in the AgentServer component. The issue has been resolved in praisonaiagents version 1.6.58. Users are strongly advised to upgrade immediately to mitigate the risk of unauthorized access to their multi-agent systems.
Bekijk origineel advisory →CVE-2026-16231 affects hbs, an Express view engine wrapping Handlebars, versions 2.1.0 through 4.2.1. The vulnerability exists in the registerAsyncHelper API, which bypasses Handlebars' automatic HTML escaping mechanism. During the first render pass, async helpers return an opaque placeholder that gets escaped, but the actual return value is substituted without escaping after rendering. This flaw affects cached, uncached, and layout render paths. Attackers can inject arbitrary HTML and JavaScript into server-rendered pages if attacker-controlled data is passed into async helper callbacks. The vulnerability enables both stored and reflected cross-site scripting (XSS) attacks. The issue is fixed in version 4.3.0, which properly HTML-escapes async helper output. Applications requiring raw HTML output can use hbs.SafeString to explicitly opt in. Users are strongly advised to upgrade to version 4.3.0 immediately.
Bekijk origineel advisory →NLTK versions before 3.10.3 contain a critical remote code execution vulnerability in their allowlisted pickle loaders. The flaw exists because the loaders trust entire module namespaces rather than restricting access to specific safe callables. Attackers can craft malicious pickle payloads that invoke dangerous functions such as ReppTokenizer._execute and numpy.f2py.crackfortran.myeval via the pickle REDUCE opcode. Exploitation occurs during the loading of model or tokenizer artifacts, making supply chain and model-sharing scenarios particularly risky. The vulnerability allows arbitrary command execution on affected systems. Users are urged to upgrade to NLTK 3.10.3 or later to remediate the issue. Details are available via NVD, the NLTK GitHub security advisory, and VulnCheck.
Bekijk origineel advisory →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 →