Vulnerabilities exploitable today
376,337in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,713
New KEV · 24H0
Exploit Today ≥ 701,646
Distribution · last window
- Critical2,379
- High8,722
- Medium6,763
- Low724
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-630468.8 HIG30.0%
——9Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability in Apache InLong. Agent Installer's ModuleManager executes arbitrary shell
commands via ExcuteLinux.exeCmd() with no filtering or whitelist
validation.
This issue affects Apache InLong: from 2.0.0 before 2.4.0.
Users are advised to upgrade to Apache InLong's 2.4.0 or cherry-pick [1]/[2] to solve it.
[1] https://github.com/apache/inlong/pull/12151 .
[2] https://github.com/apache/inlong/pull/12155 .22dCVE-2019-18391—30.0%
——9——CVE-2026-25722—30.0%
——9——CVE-2008-5150—30.0%
——9——CVE-2026-474178.1 HIG30.0%
——9PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The comment endpoints (`POST /workspaces/{workspace_id}/issues/{issue_id}/comments` and `GET .../comments`) gate access on `require_workspace_member(workspace_id)` only, then call `CommentService.create(issue_id=issue_id, ...)` and `CommentService.list_for_issue(issue_id)` without verifying that `issue_id` belongs to `workspace_id`. A user who is a member of any workspace `W1` can read every comment on, and post new comments to, any issue in any other workspace `W2`. PraisonAI Platform version 0.1.4 patches the issue.59dCVE-2023-29637—30.0%
——9——CVE-2002-1672—30.0%
——9——CVE-2019-8528—30.0%
——9——CVE-2023-460355.9 MED30.0%
——9The svg_optimizer gem before 0.3.0 for Ruby performs entity expansion on untrusted documents.4dCVE-2023-36405—30.0%
——9——CVE-2025-5377—30.0%
——9——CVE-2026-832848.6 HIG30.0%
——9Vulnerability in the Oracle BI Publisher product of Oracle Analytics (component: BI Platform Security). Supported versions that are affected are 8.2.0.0.0, 12.2.1.4.0 and 26.01.0.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via SOAP to compromise Oracle BI Publisher. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle BI Publisher as well as unauthorized update, insert or delete access to some of Oracle BI Publisher accessible data and unauthorized read access to a subset of Oracle BI Publisher accessible data. CVSS 3.1 Base Score 8.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H).2dCVE-2024-43376—30.0%
——9——CVE-2025-1807—30.0%
——9——CVE-2026-691068.8 HIG30.0%
——9A low-privileged user may poison cached artifact metadata under specific conditions, potentially causing consumers to retrieve untrusted content.7dCVE-2026-165486.5 MED30.0%
——9The Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat WordPress plugin before 1.8.2 does not validate the type, extension, content, or size of files submitted to its public response endpoint and stores them under the uploads directory, so an unauthenticated user can upload arbitrary files. The original extension is discarded (files are stored under a bare UUID), so this does not yield code execution or stored XSS; impact is bounded to disk consumption and content hosting. The storing path requires the channel's response storage or mail-forwarding to be configured.23dCVE-2025-14833—30.0%
——9——CVE-2025-29922—30.0%
——9——CVE-2025-2084—30.0%
——9——CVE-2019-25460—30.0%
——9——CVE-2026-42368—30.0%
——9——CVE-2024-45690—30.0%
——9——CVE-2026-2706—30.0%
——9——CVE-2011-4325—30.0%
——9——CVE-2013-2391—30.0%
——9——CVE-2026-226618.1 HIG30.0%
——9prompts.chat prior to commit 0f8d4c3 contains a path traversal vulnerability in skill file handling that allows attackers to write arbitrary files to the client system by crafting malicious ZIP archives with unsanitized filenames containing path traversal sequences. Attackers can exploit missing server-side filename validation to inject path traversal sequences ../ into skill file archives, which when extracted by vulnerable tools writing files outside the intended directory and overwriting shell initialization files to achieve code execution.56dCVE-2025-64091—30.0%
——9——CVE-2023-40261—30.0%
——9——CVE-2026-545269.9 CRI30.0%
——9Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 3.7.15 and 4.0.6, the allow-list fix for CVE-2026-31892 is incomplete because workflow/util/merge.go ValidateUserOverrides and SanitizeUserWorkflowSpec walk only the top-level fields of WorkflowSpec via reflection, and WorkflowSpec.ArtifactGC is allow-listed wholesale; the struct behind that field, WorkflowLevelArtifactGC, has a PodSpecPatch sub-field whose contents flow unmodified into util.ApplyPodSpecPatch on the artifact-GC pod, the same sink the original fix closed for WorkflowSpec.PodSpecPatch, so a user submitting a Workflow under templateReferencing: Strict or Secure (against a referenced WorkflowTemplate that declares an output artifact and setting spec.artifactGC.strategy: OnWorkflowCompletion) can still inject an arbitrary strategic merge patch into the artifact-GC pod, including hostPath volumes, privileged: true, arbitrary image and command, and hostNetwork: true, defeating the stated purpose of Strict/Secure reference mode. This issue is fixed in versions 3.7.15 and 4.0.6.50dCVE-2015-5843—30.0%
——9——CVE-2025-23539—30.0%
——9——CVE-2018-10505—30.0%
——9——CVE-2015-5848—30.0%
——9——CVE-2013-1918—30.0%
——9——CVE-2008-6398—30.0%
——9——CVE-2002-2000—30.0%
——9——CVE-2023-40454—30.0%
——9——CVE-2025-23570—30.0%
——9——CVE-2025-23556—30.0%
——9——CVE-2020-5825—30.0%
——9——