CVE-20XX-?
agent?

Other CVEs.

Published CVEs that affect other software, ranked by exploit odds.

473 CVEs · updated 2026-11-20 20:10 UTC

Reset all
  1. CVE-2026-111498

    OpenManage Enterprise, versions prior to 4.8.0, contains an Improper Resource Locking vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Protection mechanism bypass.

    Other Dell Openmanage Enterprise

    4.7 MEDIUM 0.1% exploit odds Fix listed
  2. CVE-2026-129919

    Kunai, a security monitoring tool, contains a time-of-check to time-of-use (TOCTOU) race condition in its mount namespace (mnt ns) caching logic. When resolving a security event that references a specific process PID and an expected mount namespace, the Switcher::new function read /proc/<pid>/ns/mnt to determine the target namespace and cached the result under the expected namespace key without verifying that the resolved namespace actually matched the expected one. An attacker with local access could exploit this by either (1) arranging for the referenced PID to be reused by a process in a different namespace (e.g., the host namespace) before Kunai resolves it, or (2) calling unshare or setns on the target process after the event is generated but before the namespace is resolved. In either case, the wrong namespace (potentially the host's own namespace) would be cached under the container's namespace key. The security impact is that subsequent container security events would be resolved against host filesystem paths rather than container paths. This undermines the integrity of the security monitoring data: container activity could be misattributed to the host, host activity could be misattributed to a container, and file-path-based detections or alerts would reference incorrect paths. An attacker could potentially use this to obscure malicious activity within a container by making it appear as benign host activity, or to generate misleading security alerts. The vulnerability requires local access to the system and a specific timing window between event generation and namespace resolution. No remote attack vector or user interaction is required.

    Other

    2.0 LOW 0.1% exploit odds Fix listed
  3. CVE-2026-66986

    HCL AION is affected by a vulnerability where user sessions did not expire after a sufficient period of inactivity. An unattended authenticated session could be used by another person with access to the same system to view information or perform actions on behalf of the user, potentially resulting in unintended behavior or security impact under certain conditions.

    Other

    3.3 LOW 0.1% exploit odds No fix listed
  4. CVE-2026-58886

    In updateInputWindows of InputMonitor.java, there is a possible tapjacking issue due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

    Other Google Android

    7.8 HIGH 0.1% exploit odds Fix listed
  5. CVE-2026-55257

    In UsbDialogHelper of UsbDialogHelper.java, there is a possible UI confusion due to misleading or insufficient UI. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  6. CVE-2026-28597

    In writeGrantedUriPermissions of UriGrantsManagerService.java, there is a possible permission bypass due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  7. CVE-2026-112602

    An authorization issue was addressed with improved state management. This issue is fixed in Xcode 27.2. An app may be able to access sensitive user data.

    Other

    3.3 LOW 0.1% exploit odds Fix listed
  8. CVE-2026-118464

    Shared cryptographic services use fixed vendor-wide secrets, deterministic IVs, null salts, and reversible transformations to protect credentials, IPC data, configuration values, and clinical fields.

    Other

    5.8 MEDIUM 0.1% exploit odds No fix listed
  9. CVE-2026-127348

    Vulnerability in the Oracle Hyperion Financial Close Management product of Oracle Hyperion (component: Reconciliation Manage). The supported version that is affected is 11.2.26.0.000. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Hyperion Financial Close Management executes to compromise Oracle Hyperion Financial Close Management. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Hyperion Financial Close Management accessible data as well as unauthorized read access to a subset of Oracle Hyperion Financial Close Management accessible data. CVSS 3.1 Base Score 3.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N).

    Other

    3.6 LOW 0.1% exploit odds No fix listed
  10. CVE-2026-130899

    Tanium addressed a time-of-check time-of-use race condition vulnerability.

    Other Tanium Endpoint Configuration Toolset Solution

    2.5 LOW 0.1% exploit odds No fix listed
  11. CVE-2026-82138

    Dell SupportAssist OS Recovery, versions prior to 5.5.16.3 contain a Download of Code Without Integrity Check vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Code execution.

    Other Dell SupportAssist OS Recovery

    7.4 HIGH 0.1% exploit odds Fix listed
  12. CVE-2026-58970

    In deliverResult of AppTimeTracker.java, there is a possible background activity launch due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other

    8.4 HIGH 0.1% exploit odds No fix listed
  13. CVE-2026-58957

    In resolveToHeavyWeightSwitcherIfNeeded of ActivityStarter.java, there is a possible background activity launch due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  14. CVE-2026-58943

    In run of AddAccountSettings.java, there is a possible background activity launch due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  15. CVE-2026-58944

    In moveTaskToFrontLocked of ActivityTaskManagerService.java, there is a possible background application launch (bal) issue due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  16. CVE-2026-55271

    In forwardToPreferredActionPickHandler of ContactsPickerActivity.kt, there is a possible intent redirection due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  17. CVE-2026-49931

    In onActivityResult in multiple locations, there is a possible contact leak from protected profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  18. CVE-2026-129092

    CCC Attestation SIG attested-tls-poc through commit 731ca82 contains a time-of-check time-of-use vulnerability because Evidence is appraised only once during the TLS handshake, without post-handshake re-attestation. Attackers with local access to the attesting endpoint can alter workload code, data, configuration, or attached devices like GPUs while peers keep trusting the original Evidence.

    Other CCC-Attestation attested-tls-poc

    7.0 HIGH 0.1% exploit odds No fix listed
  19. CVE-2026-118373

    LibreSSL ocspcheck through 4.4.0 contains a cleartext transmission vulnerability because url2host() discards the OCSP URL scheme and http_alloc() only selects TLS for port 443. On-path network attackers can read OCSP requests sent to https responder URLs on non-443 ports, exposing certificate serial numbers, issuer hashes, and nonces.

    Other

    6.3 MEDIUM 0.1% exploit odds Fix listed
  20. CVE-2026-116844

    Fclairamb ftpserverlib through 0.32.4 contains a cleartext transmission vulnerability because TransferOpen checks only the transferTLS flag set by PROT, not whether the prepared data connection uses TLS. When a client sends PROT P after PASV or PORT, file contents and directory listings cross the network unencrypted, even with mandatory encryption, letting on-path attackers read or modify them.

    Other

    6.3 MEDIUM 0.1% exploit odds Fix listed
  21. CVE-2026-130750

    Network-AI from 5.11.0 before 5.17.2 contains a CORS misconfiguration in McpStreamableServer that reflects localhost Origins into Access-Control-Allow-Origin regardless of bind interface. Attackers controlling a localhost-origin page or DNS-rebinding name can read unauthenticated /tools and /health responses, exposing tool catalogs and bridge metadata on non-loopback binds.

    Other Jovancoding Network-AI

    6.9 MEDIUM 0.1% exploit odds Fix listed
  22. CVE-2026-28665

    In onCreate of SettingsApplication.java, there is a possible cross-profile consent dialog label injection due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  23. CVE-2026-114217

    A flaw was found in konflux-ci. Continuous Integration (CI) automation scripts store sensitive GitHub access tokens in plaintext on the runner without cleaning them up after execution. A local attacker with access to the CI environment can read these stored credentials to gain unauthorized repository access, potentially allowing them to modify source code or release artifacts.

    Other

    8.6 HIGH 0.1% exploit odds No fix listed
  24. CVE-2026-71534

    Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, restore logic in mareforma/db/restore.py derives transparency_logged from the unsigned rekor.uuid field inside signature_bundle without requiring a verified claim-bound rekor_inclusions entry, so an attacker who modifies claims.toml can falsely make a claim eligible for REPLICATED convergence. The same logic resets signed claims in non-Rekor graphs from transparency_logged 1 to 0 after restore, permanently preventing convergence because no Rekor refresh is configured. This issue is fixed in version 0.3.8.

    Other Mareforma

    6.9 MEDIUM 0.1% exploit odds Fix listed
  25. CVE-2025-22436

    In multiple locations, there is a possible way to trick a user into disclosing Autofill contents due to a tapjacking/overlay attack. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  26. CVE-2026-58961

    In moveTaskToFrontLocked of ActivityTaskManagerService.java, there is a possible background activity launch due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  27. CVE-2026-131845

    Poppler 21.01.0 through 26.11.0 contains a time-of-check time-of-use race condition in FormWidgetSignature::signDocument() that allows local attackers to obtain valid signatures over altered content. Attackers with write access to the output file or directory can overwrite or swap the PDF between writing and hashing, causing the signer's key to sign attacker-controlled content.

    Other Freedesktop Poppler

    4.1 MEDIUM 0.1% exploit odds No fix listed
  28. CVE-2026-58964

    In checkDestination of SmsUsageMonitor.java, there is a possible permission bypass due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  29. CVE-2026-92606

    Time-of-check time-of-use (TOCTOU) race condition vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute Pardus MyComputer allows Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions. This issue affects Pardus MyComputer: from 0.8.0 before 0.8.1.

    Other

    6.0 MEDIUM 0.1% exploit odds No fix listed
  30. CVE-2026-116196

    Rclone before v1.75.2 contains a credential exposure vulnerability in the b2 backend that leaks the live account Authorization token and SSE-C keys on HTTP redirects from --b2-download-url hosts. Attackers can observe a same-host HTTPS-to-HTTP downgrade redirect to capture the cleartext B2 token, or receive cross-host redirects disclosing SSE-C customer encryption keys.

    Other Rclone

    6.0 MEDIUM 0.1% exploit odds Fix listed
  31. CVE-2026-77389

    pmo-platform is a modular PMO and release-management platform for Claude Code. Prior to 3.73, core/hooks/block-fragile-refs.sh and core/hooks/block-gh-path-leak.sh source co-shipped awk primitives from core/hooks/lib/ and degrade when a required primitive is absent. In a partial or corrupted deployment, block-gh-path-leak.sh skips its entire path-leak check, while block-fragile-refs.sh skips only the positional-issue-reference detector and continues running its other detectors. Both hooks operate in a warning posture, so the impact is a skipped warning rather than bypass of an enforcing control, with no established exfiltration or code-execution primitive. This issue is fixed in version 3.73.

    Other cody-hutson pmo-platform

    2.0 LOW Fix listed
  32. CVE-2026-62319

    Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 1.5.0 until 4.5.1, dsi_stream_receive in libatalk/dsi/dsi_stream.c independently clamps dsi_doff and dsi_len for DSIWrite requests without enforcing that the data offset is no greater than the declared frame length. An authenticated AFP client can send dsi_doff greater than dsi_len, causing the receiver to consume bytes from a queued subsequent frame before libatalk/dsi/dsi_write.c detects the inconsistency. The irreversible stream desynchronization lets the attacker control the next parsed DSI header and payload and corrupts protocol framing for the connection. This issue is fixed in version 4.5.1.

    Other Netatalk

    7.2 HIGH Fix listed
  33. CVE-2026-77332

    memtomem-stm is a short-term memory proxy gateway with proactive memory surfacing for AI agents. From 0.1.0 until 0.1.34, untrusted long-term and working-memory fields can introduce Markdown or HTML-compatible structure into the surfaced-memory envelope because those fields are not serialized as inert data. A crafted memory can create misleading structural boundaries or visually conceal surfaced content, affecting how a consuming agent interprets the memory context. Ordinary natural-language persuasion remains a residual model-level risk and is outside the structural serialization flaw. This issue is fixed in version 0.1.34.

    Other Memtomem memtomem-stm

    2.3 LOW Fix listed
  34. CVE-2026-77331

    memtomem-stm is a short-term memory proxy gateway with proactive memory surfacing for AI agents. From 0.1.2 until 0.1.34, concurrent surfacing RPC failures can start more than one reconnect for the same dirty session because concurrent LTM recovery is not uniquely owned by a session generation. Cancellation during a post-reconnect retry can also leave the replacement transport reusable after an interrupted protocol exchange, causing session-state integrity loss or local service degradation. The duplicate-reconnect subcase was introduced in 0.1.24, while the cancellation-recovery subcase affects the broader listed range. This issue is fixed in version 0.1.34.

    Other Memtomem memtomem-stm

    2.0 LOW Fix listed
  35. CVE-2026-133702

    free5GC PCF through 1.4.6 contains a resource leak in postAppSessCtxProcedure that leaves PCC rules and QoS data in the SM policy decision after rejected Npcf_PolicyAuthorization create requests. Authenticated AFs knowing an active PDU session's UE address can send repeated failing requests with distinct AF application identifiers to grow PCF memory and pollute policy sent to the SMF.

    Other free5gc Pcf

    5.3 MEDIUM Fix listed
  36. CVE-2026-133700

    free5GC SMF through 1.4.6 contains a resource leak vulnerability in HandlePDUSessionSMContextCreate that leaves SM contexts unreleased when UDM access token retrieval fails. Attackers can trigger repeated PDU session establishment attempts while the NRF is unreachable, causing empty 200 responses and persistent SMF memory growth.

    Other free5gc Smf

    2.3 LOW Fix listed
  37. CVE-2026-101340

    Net::DNS uses a 16-bit query ID to match responses to the corresponding requests. In versions up to and including 1.57, the ID is obtained from Perl's built-in rand() function. An attacker that can observe the sequence of query IDs is able to expose the internal state of the PNRG and hence predict query IDs before they are transmitted. The victim Net::DNS instance is then exposed to forged responses injected by the attacker. Note that the deduplication cache in 1.57 has no impact on the feasibility of this attack.

    Other NLnet Labs Net::DNS

    9.1 CRITICAL Fix listed
  38. CVE-2026-133627

    flowintel contains a log injection vulnerability in its case history (audit log) subsystem. The case history is stored as a line-delimited file where each line represents a single event attributed to a specific user. User-controlled fields, including user names, event messages, and case titles used during case merging, were written to the history file without sanitizing embedded line separator characters (such as carriage return, line feed, vertical tab, form feed, and Unicode line/paragraph separators). An authenticated user with the ability to create or modify case history entries could embed line separators in these fields. Upon writing, the injected separators would split a single intended entry into multiple lines, each of which the history format interprets as a distinct event. This allows an attacker to forge additional history entries attributed to arbitrary users, corrupting the audit trail and undermining the integrity of case records. The vulnerability affects the case history append and merge operations. No authentication bypass or privilege escalation is required beyond normal case-management access. Affected versions: flowintel prior to 4.1.0.

    Other Flowintel

    5.3 MEDIUM Fix listed
  39. CVE-2026-133422

    Validating an untrusted list into a field constrained with unique_items=True with Pydantic V1 takes quadratic time: an input of a few hundred kilobytes takes seconds to validate. The ConstrainedList.unique_items_validator validator (in pydantic/types.py) checks each item against all the following ones. For a list with no duplicates (the common, valid case), this results in a quadratic number of comparisons. The issue was fixed in commit 6ec75e57f277a820ec583e601167f25fe8dc7c87. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later. Impact: denial of service through validation of untrusted input. Affected are applications validating untrusted lists into fields constrained with unique_items=True (using conlist() or Field()). The fix only applies to lists of builtin scalar types (int, float, str, bytes, bool and None), for which duplicates can be detected in linear time. Lists of other types (e.g. models or dictionaries) are still checked in quadratic time, as their items aren't guaranteed to be hashable: bound their size using the max_items constraint. Pydantic V2 models are not affected.

    Other Pydantic

    6.9 MEDIUM Fix listed
  40. CVE-2026-133424

    When extra data is allowed, providing both the alias and the name of an aliased TypedDict or dataclass field makes the unvalidated value (provided under the name) overwrite the validated one (provided under the alias), resulting in validated data not matching the declared type. Extra items are stored in the same dictionary as the fields (the returned dictionary for TypedDict, the instance __dict__ for dataclasses). As only the alias is marked as used, the field name is treated as an extra item, and its unvalidated value overrides the validated one. The TypedDict validator (pydantic-core/src/validators/typed_dict.rs) and the dataclass validator (pydantic-core/src/validators/dataclass.rs) share this logic. The issue was fixed in commit 34491f5328f168f14e3769cd5f0f83c0af0f4778. Impact: validation bypass, as data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into TypedDict or dataclass types with aliased fields and extra data allowed (with extra='allow', or with the extra_items argument for TypedDict), using Pydantic V2 (up to and including 2.14.1). Pydantic models (BaseModel) are not affected, as extra data is stored separately from fields.

    Other Pydantic

    6.3 MEDIUM Fix listed
  41. CVE-2026-133429

    When validating JSON data into a model allowing extra data, the keys of extra data aren't validated against the key type annotated on __pydantic_extra__, resulting in extra data not matching the declared type. This is the case if you define __pydantic_extra__ as e.g. dict[Annotated[str, Field(pattern=r'^x_')], int]. The validate_json_by_iteration() method (in pydantic-core/src/validators/model_fields.rs), used to validate JSON data into models, only validates the values of extra data, and stores the keys as is. The issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358. Impact: validation bypass, as extra data returned by validation doesn't match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra='allow'), with a key type annotated on __pydantic_extra__ (e.g. dict[Annotated[str, Field(pattern=...)], int]), using Pydantic from 2.13.0 up to (but excluding) 2.14.2. Python mode validation isn't affected.

    Other Pydantic

    6.3 MEDIUM Fix listed
  42. CVE-2026-133490

    A vulnerability was detected in declare-lab tango up to 34ecd38898508017ca937508a047b42817d2b070. Impacted is the function Tango.__init__ of the file tango.py of the component Model Loading. Performing a manipulation of the argument scheduler_name results in improper input validation. The attack is possible to be carried out remotely. The exploit is now public and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

    Other declare-lab Tango

    2.1 LOW No fix listed
  43. CVE-2026-65094

    NVIDIA VIRTIO-Net for Bluefield contains a vulnerability in Virtio-Net where a VM user may cause a Write-What-Where condition by crafted message. A successful exploit of this vulnerability may lead to Code Execution in Virtio-Net scope.

    Other NVIDIA VIRTIO-Net GA

    9.0 CRITICAL No fix listed
  44. CVE-2026-24205

    NVIDIA TensorRT-LLM for any platform contains a vulnerability where a user may cause a race condition by running concurrent requests. A successful exploit of this vulnerability may lead to data tampering.

    Other NVIDIA TensorRT-LLM

    6.4 MEDIUM No fix listed
  45. CVE-2026-84211

    IBM Guardium Data Protection 12.2 could allow a remote attacker to inject forged audit records due to improper output neutralization for logs.

    Other IBM Guardium Data Protection

    5.9 MEDIUM Fix listed
  46. CVE-2026-76545

    In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could determine whether a username exists through the Representational State Transfer (REST) API or Splunk Web and lock out existing user accounts through repeated login attempts. The vulnerability is possible because Splunk Enterprise returns different login failure responses for locked existing user accounts and nonexistent usernames.

    Other Splunk Enterprise

    6.5 MEDIUM No fix listed
  47. CVE-2026-18883

    ServiceNow has addressed an indirect prompt injection security issue that was identified in the Email Response AI Agent of Now Assist for CSM. We are not currently aware of malicious exploitation against ServiceNow instances. This remediation was deployed centrally to the Email Response AI Agent (Now Assist for CSM) and does not require a platform version upgrade or hot fix; no version-specific backports apply.

    Other ServiceNow Now Assist For CSM

    7.1 HIGH No fix listed
  48. CVE-2026-131298

    In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission on a workbook could configure a service-level agreement at only the workbook phase or task level. Splunk SOAR then flags the task as overdue immediately and does not display the configured deadline in the work queue. The incorrect deadline status could obscure genuine deadline breaches. The vulnerability is possible because Splunk SOAR treats an absent phase-level or task-level service-level agreement as immediately due when it compares the configured due times. For more information see Define tasks using workbooks (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/7.0.0/configure-product-settings-for-your-splunk-soar-on-premises-instance/define-tasks-using-workbooks) in the Splunk documentation.

    Other Splunk SOAR

    4.3 MEDIUM No fix listed
  49. CVE-2026-131283

    In Splunk SOAR versions below 8.8.0, an authenticated user with playbook edit permission could cause later playbook conversions to include spurious branch conditions. This can prevent downstream blocks from running in affected converted playbooks. The vulnerability is possible because the playbook converter retains branch conditions from previous conversions.

    Other Splunk SOAR

    4.3 MEDIUM No fix listed
  50. CVE-2026-131284

    In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers could import a container archive that makes artifacts appear to be part of a case or have notes when no corresponding case associations or notes exist. This could cause Representational State Transfer (REST) API clients and filters to use incorrect artifact state. The vulnerability is possible because container archive import accepts artifact workflow state from the archive instead of deriving that state from associated cases and notes. For more information see Splunk SOAR REST API reference (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference) in the Splunk documentation.

    Other Splunk SOAR

    4.3 MEDIUM No fix listed

CVEs that affect other, sorted by how likely they are to be exploited (EPSS).