CVE Vulnerability Catalog

In the Linux kernel's af_unix subsystem, a synchronization issue was found in the unix_gc() function. The gc_in_progress flag could be set to false while the garbage collector was still running, allowing another GC run to start prematurely. The unix_peek_fpl() function relies on this flag to avoid errors with MSG_PEEK.

A critical vulnerability in the Linux kernel's KVM/SEV component for AMD EPYC processors with SEV-SNP support. The lack of requiring the scratch area to reside in the GHCB v2+ shared buffer, combined with multiple validation flaws, allows a malicious SNP guest to perform out-of-bounds (OOB) reads and writes in the host kernel heap.

A use-after-free vulnerability was found in the Linux kernel's KVM shadow paging for x86. The bug occurs due to a role mismatch when a PDE mapping is changed from outside the guest, causing reuse of a kvm_mmu_page with an incorrect role. This leads to a dangling rmap entry after memslot deletion, and subsequent operations on the freed page cause memory corruption.

HestiaCP panel contains a broken access control vulnerability in the cronjob feature. Low privilege users can modify panel cronjobs to execute HestiaCP management scripts with passwordless sudo.

myVesta is affected by an authenticated remote code execution vulnerability. Low privileged users can inject arbitrary commands via the v_ftp_user parameter when deleting FTP usernames.

A missing authentication vulnerability was found in the AJAX Endpoint component of restaurant-website-php-mysql, specifically in the /admin/ajax_files file. Remote attackers can manipulate the endpoint without authentication. The exploit has been publicly disclosed, increasing the risk of attacks.

In nltk versions 3.9.3 and earlier, five Stanford interface classes (StanfordPOSTagger, StanfordNERTagger, StanfordParser, StanfordDependencyParser, and StanfordNeuralDependencyParser) are vulnerable to untrusted JAR code execution. These classes accept user-controllable JAR paths and execute them via the `java()` function, which invokes `subprocess.Popen()` without integrity verification. This vulnerability is identical to CVE-2026-0848, which was fixed for StanfordSegmenter by adding SHA256 verification, but the fix was not applied to these additional classes.

The Execute Command node in n8n allows authenticated users to execute arbitrary commands on the host system where n8n runs. Attackers with user access or compromised credentials can exploit this node to run malicious commands, potentially leading to data exfiltration, service disruption, or complete system compromise.

Picklescan before version 0.0.34 fails to detect the _operator.methodcaller built-in function when scanning pickle files for malicious code. Attackers can craft malicious pickle payloads using _operator.methodcaller that evade detection and execute arbitrary code when loaded by pickle.load().

The vulnerability in picklescan before version 0.0.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle payloads using operator.methodcaller that execute arbitrary code when loaded.

Picklescan before version 0.0.33 fails to detect the numpy.f2py.crackfortran.getlincoef gadget in pickle __reduce__ methods, allowing arbitrary code execution. Attackers can craft malicious pickle files that execute arbitrary Python code when loaded, bypassing Picklescan's safety checks.

Picklescan before version 0.0.28 fails to detect malicious pickle files that use torch.utils.data.datapipes.utils.decoder.basichandlers in reduce methods, allowing attackers to bypass safety checks. Remote attackers can embed undetected malicious code in pickle files that executes during deserialization, enabling remote code execution.

The vulnerability in picklescan before version 0.0.34 fails to detect _operator.attrgetter function calls in pickle payloads, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle files using _operator.attrgetter in reduce methods to execute arbitrary code when pickle.load() processes the file.

The vulnerability in picklescan before version 0.0.28 fails to detect malicious torch.utils.bottleneck.__main__.run_cprofile function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can embed undetected code in pickle files to achieve arbitrary code execution when victims load the files.

Picklescan before version 0.0.30 fails to detect the asyncio.unix_events._UnixSubprocessTransport._start function in pickle reduce methods, allowing remote code execution. Attackers can craft malicious pickle files embedding this built-in function that evade detection but execute arbitrary commands when loaded.

Picklescan before version 0.0.33 fails to detect unsafe deserialization when numpy.f2py.crackfortran functions call eval on arbitrary strings. Attackers can embed malicious code in pickle files that executes when loaded from untrusted sources.

A vulnerability in picklescan before version 0.0.29 fails to detect malicious pickle files using the idlelib.calltip.get_entity function in reduce methods. Attackers can embed undetected code in pickle files that executes remote commands when loaded by victims.

The vulnerability in picklescan before version 0.0.29 fails to detect malicious pickle payloads that use lib2to3.pgen2.grammar.Grammar.loads in the reduce method, allowing remote code execution. Attackers can craft pickle files embedding dangerous code that evades picklescan detection and executes during pickle.load() deserialization.

Picklescan before version 0.0.28 fails to detect malicious torch.fx.experimental.symbolic_shapes.ShapeEnv.evaluate_guards_expression function calls in pickle files. Attackers can embed undetected code in pickle files that executes remote code when loaded by victims.