PULSE
FEED
ransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomsilentransomgroup reclama a Kutak Rock LLP · US · Professional Servicesransomincransom reclama a CHAMBOURCY · FR · Government & Defenseransomhandsome boy hacking club reclama a UCHealth · US · Healthcareransomhandsome boy hacking club reclama a Smith & Wesson · US · Manufacturingransomdeadlock reclama a MedMira Inc · CA · Healthcareransomrhysida reclama a Rober & Phillipsransomsoulgroup reclama a SHOPBOT TOOLS, INC. · US · Retail & E-Commerceransomsoulgroup reclama a Noble Inc. · US · Energy & Utilitiesransomsoulgroup reclama a United Medical Doctors · US · Healthcareransomsoulgroup reclama a METO Systems · US · Technologyransomsoulgroup reclama a Nephrology Associates · US · Healthcareransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomsilentransomgroup reclama a Kutak Rock LLP · US · Professional Servicesransomincransom reclama a CHAMBOURCY · FR · Government & Defenseransomhandsome boy hacking club reclama a UCHealth · US · Healthcareransomhandsome boy hacking club reclama a Smith & Wesson · US · Manufacturingransomdeadlock reclama a MedMira Inc · CA · Healthcareransomrhysida reclama a Rober & Phillipsransomsoulgroup reclama a SHOPBOT TOOLS, INC. · US · Retail & E-Commerceransomsoulgroup reclama a Noble Inc. · US · Energy & Utilitiesransomsoulgroup reclama a United Medical Doctors · US · Healthcareransomsoulgroup reclama a METO Systems · US · Technologyransomsoulgroup reclama a Nephrology Associates · US · Healthcare
← All CVEs
CVE WatchNov 19, 2026

CVE-2026-133184

MISP contains an authorization and input-validation flaw in its event push mechanism. When a user with push permissions initiates a push of

CVSS

—

No CVSS

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 19, 2026 · Last modified: Nov 19, 2026 · CWE-20 · CWE-862

EPSS · 30d

Not enough EPSS history yet.

Technical description

MISP contains an authorization and input-validation flaw in its event push mechanism. When a user with push permissions initiates a push of events to a remote MISP instance, the system fails to enforce two critical checks: (1) it does not verify that an event is published before including it in the push, allowing unpublished (i.e., not yet publicly shared) events to be transmitted to the remote server; and (2) it does not verify that the pushing user has read access to the event, causing events the user cannot fetch to be sent as empty event shells, thereby disclosing the existence and metadata of events the user is not authorized to view. Additionally, the remote server's reply selecting which offered events to accept is used without validating that the selected identifiers actually correspond to events in the offered set, potentially allowing the remote to reference events outside the intended scope. The vulnerability requires an authenticated user with push permissions on the source MISP instance and a configured push target. The security impact is unauthorized disclosure of confidential threat-intelligence data (unpublished events and events restricted by user permissions) to a remote MISP instance that should not receive them.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1334944.3 MED
—
———Greenbone gvmd before 26.43.0 does not restrict certificate creation. Even the Observer role, documented to be read-only, can execute create_tls_certificate.4h
CVE-2026-765408.8 HIG
—
———In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user access or modify data and disrupt the Splunk Enterprise instance. The vulnerability occurs because Splunk Enterprise does not enforce the required role-based authorization when it processes metric alert configuration through the REST API. Splunk Enterprise schedules the resulting search with elevated authorization and runs attacker-controlled search processing with that authorization. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.6h
CVE-2026-765374.3 MED
—
———In Splunk Enterprise versions below 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who does not hold a role with either the list_indexer_cluster capability or the edit_indexer_cluster capability could download the cluster manager configuration bundle through the Representational State Transfer (REST) API and access configuration and app files that the cluster manager stages for indexer distribution. The vulnerability is possible because the REST API does not require the list_indexer_cluster or edit_indexer_cluster capability before it sends the configuration bundle. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation. For more information see Cluster endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.6/cluster-endpoints/cluster-endpoint-descriptions) in the Splunk documentation.5h
CVE-2026-765344.7 MED
—
———In Splunk Enterprise for Windows versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_user capability could create multiple user accounts that share the same user directory. This could expose user-specific configuration between those accounts, let one account modify configuration used by another account, or disrupt features that depend on separate user directories. The vulnerability is caused by improper validation of usernames before Splunk Enterprise performs Windows filesystem operations. Windows removes trailing periods from directory names, so distinct usernames can resolve to the same user directory. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.6h
CVE-2026-1313037.1 HIG
—
———In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain limited information about indexes and data sources outside their authorized scope through the assistant. The vulnerability is possible because Splunk AI Assistant does not fully apply authorization controls to all information that it retrieves.6h
CVE-2026-1313024.3 MED
—
———In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could turn on the AI chat training-data consent setting through the Representational State Transfer (REST) API. The missing authorization is possible because the affected configuration endpoint does not enforce authorization checks.6h