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
← Todos os CVEs
CVE Watch19 de nov. de 2026

CVE-2026-133165

MISP contains an authorization and scope flaw in the ObjectReference model's captureReference method. When a user saves an event (via REST A

CVSS

—

Sem CVSS

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 19 de nov. de 2026 · Última mod.: 19 de nov. de 2026 · CWE-639 · CWE-640

EPSS · 30d

Ainda não há histórico EPSS suficiente.

Descrição técnica

MISP contains an authorization and scope flaw in the ObjectReference model's captureReference method. When a user saves an event (via REST API, sync, or feeds), any object reference included in the payload is looked up by its UUID across the entire MISP instance rather than being scoped to the event being saved. An authenticated user with permission to add or edit events can therefore include the UUID of an object reference belonging to a different event—including events in other organizations that the user cannot view—and cause the system to overwrite that foreign reference's relationship_type, comment, deleted flag, and timestamp with attacker-supplied values. The affected reference is neither deleted nor recreated in the attacker's event; its fields are silently rewritten in place. This constitutes a cross-tenant integrity violation: data integrity of object references in events the attacker has no read or write access to is compromised. The vulnerability is reachable through any event save path (REST add/edit, inter-instance sync, feed ingestion) and requires only a valid authenticated session with event modification privileges and knowledge or discovery of a target reference UUID.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-163194.3 MÉD
—
———IBM API Connect 10.0.8.0 through 10.0.8.13 could allow a remote authenticated attacker to delete API keys belonging to other users due to improper authorization checks.5h
CVE-2026-1313048.1 ALT
—
———In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access data associated with another tenant and cause actions to be attributed to that tenant through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request.5h
CVE-2026-1312978.1 ALT
—
———In Splunk SOAR versions below 8.8.0, an operator of a configured identity provider could authenticate as an existing user associated with another configured identity provider. If that account has the "Administrator" Splunk SOAR role, the operator could control the Splunk SOAR deployment. Splunk SOAR does not bind external user accounts to the identity provider that provisions them and authenticates accounts by username without verifying provider ownership. The vulnerability requires more than one configured external identity provider with distinct trust domains and a target username that an operator of a configured identity provider can authenticate through a different provider. For more information see Configure single sign-on authentication (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/manage-your-splunk-soar-on-premises-users-and-accounts/configure-single-sign-on-authentication-for-splunk-soar-on-premises) and Manage roles and permissions (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.6h
CVE-2026-1312946.5 MÉD
—
———In Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks on a container label could associate a custom-function callback with another playbook run. The callback could modify the state of a container outside the authorized scope for that user. The vulnerability is possible because Splunk SOAR does not bind playbook API requests to the trusted playbook run and container context.5h
CVE-2026-1312938.3 ALT
—
———In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could read or overwrite persisted data for playbook runs outside the authorized label, or ownership scope for that user. The affected data can include playbook inputs, prompt and block results, outputs, and secrets that playbooks save in run data. Overwriting the data could corrupt results that paused, scheduled, or parent playbook runs later use. The vulnerability is possible because the playbook automation APIs do not bind data operations to the active playbook run.4h
CVE-2026-1312926.5 MÉD
—
———In Splunk SOAR versions below 8.8.0, a user who can edit and run a playbook on a permitted label could cause Splunk SOAR to return custom-function status and callback state from another playbook run. The issue results from insufficient binding between a custom-function-status request and the playbook run that initiates it.6h