PULSE
FEED
ransompixelleaks reclama a KDBS Solutions (client hosting) · Technologyransompixelleaks reclama a Proymoda (proymoda.com.mx) · MX · Retail & E-Commerceransomhelix reclama a Veritiv · US · Manufacturingransomvortex reclama a Drive Medical - 1,442,814 records · US · Healthcareransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturingransomthegentlemen reclama a Rosenberger Legal · DE · Professional Servicesransompixelleaks reclama a KDBS Solutions (client hosting) · Technologyransompixelleaks reclama a Proymoda (proymoda.com.mx) · MX · Retail & E-Commerceransomhelix reclama a Veritiv · US · Manufacturingransomvortex reclama a Drive Medical - 1,442,814 records · US · Healthcareransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturingransomthegentlemen reclama a Rosenberger Legal · DE · Professional Services
← Todos los CVEs
CVE Watch17 nov 2026

CVE-2026-130832

GPAC before 26.07.0 contains a NULL pointer dereference vulnerability in xmt_parse_element() in src/scene_manager/loader_xmt.c that allows a

CVSS

5.5

Medio

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 17 nov 2026 · Última mod.: 17 nov 2026 · CWE-476

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

GPAC before 26.07.0 contains a NULL pointer dereference vulnerability in xmt_parse_element() in src/scene_manager/loader_xmt.c that allows attackers to crash the process via ROUTE elements. Attackers can supply a crafted XMT-A scene file placing a ROUTE element before any scene command creates an access unit, crashing MP4Box during encoding and causing denial of service.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1308295.5 MED
—
———GPAC before 26.07.0 contains a NULL pointer dereference vulnerability in xmt_new_od_link_from_node() in src/scene_manager/loader_xmt.c that allows attackers to crash the process. Attackers can supply a crafted XMT scene file with an MFURL object-descriptor link lacking an OD ID and name, crashing MP4Box for denial of service.9h
CVE-2026-1306305.5 MED
—
———GPAC 26.02.0 contains a NULL pointer dereference vulnerability in dasher_configure_pid() in src/filters/dasher.c that dereferences ds2->set without checking for NULL. Attackers can supply a crafted MPEG-2 TS file processed with MP4Box -dash to disconnect a PID and crash MP4Box, causing denial of service.9h
CVE-2026-1305886.5 MED
—
———OpenFunction through 1.2.0 contains a NULL pointer dereference vulnerability in getServingRun that allows users permitted to create Serving resources to crash the operator by omitting the triggers section. Attackers can submit a Serving with nil Spec.Triggers to crash-loop the controller-manager, halting Function and Serving reconciliation cluster-wide until the object is deleted.16h
CVE-2026-1154286.5 MED
—
——0GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with a valid agent token to cause a denial of service in the GitLab agent server (KAS) due to improper input validation.8h
CVE-2026-936725.3 MED
—
——0bt_att_find_req_by_user_data() in subsys/bluetooth/host/att.c walks every ATT channel attached to a connection and dereferences chan->req->user_data without checking chan->req. An ATT channel with no client request in flight holds chan->req == NULL — that is its normal idle state, set by att_handle_rsp() when a response resolves the transaction and tested by att_req_send_process() to pick a free channel — so the lookup reads through a NULL pointer as soon as it visits an idle channel. Every other chan->req user in the file already guards the pointer. The lookup is reached from the public bt_gatt_cancel() API and, more importantly, from the host itself: bt_gatt_unsubscribe() calls bt_gatt_cancel() while a subscribe CCC write is still outstanding (BT_GATT_SUBSCRIBE_FLAG_WRITE_PENDING), and call_notify_cb_and_maybe_unsubscribe() in subsys/bluetooth/host/gatt.c invokes bt_gatt_unsubscribe() from the RX path whenever an application notify callback returns BT_GATT_ITER_STOP. A malicious or malfunctioning peer can hold the trigger window open by withholding the ATT Write Response to the CCC write and then sending a notification for the subscribed handle. With CONFIG_BT_EATT the traversal is very likely to meet an idle sibling channel, since ATT channels are prepended to the list and a channel opened after the pending request was sent is visited first. The dereference is a read of a small constant offset from address zero, so the impact is availability only: no memory corruption, no attacker-chosen address and no information disclosure. On platforms and configurations where a near-NULL read traps — TrustZone non-secure images, MMU targets, native_sim, or builds with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_MPU/_DWT — the fault occurs in the Bluetooth RX context and results in a fatal error and device reset. On a plain Cortex-M build with the vector table mapped at address 0 and null-pointer detection disabled (the default) the read succeeds and the defect is inert. The fix adds an explicit chan->req != NULL test to the channel traversal and additionally rejects a NULL user_data argument, which would otherwise have matched, and cancelled, an unrelated request.12h
CVE-2026-936694.7 MED
—
——0The ITE IT8xxx2 SHI host-command backend in subsys/mgmt/ec_host_cmd/backends/ec_host_cmd_backend_shi_ite.c arms the SPI peripheral before its receive context exists. shi_ite_init_registers() sets the state machine to SHI_STATE_READY_TO_RECV and calls irq_enable() while the device initializes at POST_KERNEL priority CONFIG_KERNEL_INIT_PRIORITY_DEFAULT (40), but data->rx_ctx and data->tx are only assigned later by shi_ite_backend_init(), which ec_host_cmd_init() invokes at CONFIG_EC_HOST_CMD_INIT_PRIORITY (default 80). If the attached host processor starts a SPI transaction inside that window, the Rx-valid-length interrupt fires, shi_ite_int_handler() passes its state check and calls shi_ite_parse_header(), which stores the host-derived request length through the still-NULL data->rx_ctx. On the IT8xxx2 low addresses are not backed by RAM, and with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_PMP the first bytes of the address space are explicitly made inaccessible, so the store raises a fatal access fault in interrupt context. The window widens further when CONFIG_EC_HOST_CMD_INITIALIZE_AT_BOOT is disabled and the application calls ec_host_cmd_init() itself. The result is a kernel panic on the embedded controller: with Zephyr's default fatal handler the CPU halts, so the controller stops servicing host commands until a hardware reset. Because the trigger is traffic from the attached host processor -- an untrusted peer from the controller firmware's point of view -- software on that host can provoke the fault by forcing a controller reset and issuing transactions during the reboot, turning a recoverable reset into a persistent outage. Impact is limited to availability: the faulting address is fixed and not attacker-chosen, so no memory-corruption primitive follows. The fix leaves the interface at SHI_STATE_DISABLED with the interrupt masked during device init, moves irq_enable() into shi_ite_backend_init() after the buffers are published, and makes shi_ite_int_handler() reject a NULL data->rx_ctx while write-clearing IT83XX_SPI_ISR and IT83XX_SPI_RX_VLISR so that an unexpected early interrupt cannot storm.12h