Connected evidence
Follow a shared identifier, source page or planning group across source records. Dates show chronology; a connection does not establish cause, a shared rollout or applicability to your environment.
Saved searches 0
Keep up to eight named searches. Saved in this browser. Filters are also shareable in the page address.
Threads
Related changes across sources- In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the four non-secure-callable secure stack functions of the TrustZone-M ports dereference a thread pointer supplied by the non-secure world without checking that it points to non-secure… Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- Lack of traffic encryption in Płatnik Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- Weak password encoding in Płatnik Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- Use of Client-Side Authentication in Płatnik Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- WordPress FV Flowplayer Video Player plugin <= 8.3.4 - PHP Object Injection vulnerability Affected-version evidence changed: WordPress FV Flowplayer Video Player plugin <= 7.5.56.7212 - PHP Object Injection vulnerability2 linked entries across history · in Security Follow evidence and connection reasons
- Attendo Admin Android 3.0.13 Hard-coded MQTT Broker Credentials Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- HotGo through 2.15.1 Authentication Bypass via Client-Set SMS Verification Code Affected-version evidence changed: HotGo 2.8.4 through 2.15.1 Authentication Bypass via Client-Set SMS Verification Code2 linked entries across history · in Security Follow evidence and connection reasons
- CVE-2026-120656 Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- Org.jboss.resteasy/resteasy-core: resteasy: information disclosure through default exception mapper responses Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- Elo: Code injection in Elo backends via unvalidated emission of programmatic AST fields Newly collected advisory2 linked entries across history · in Security Follow evidence and connection reasons
- Elo: Remote Code Execution in Elo Ruby backend via unescaped `#{...}` interpolation in emitted string literals and subtype-constraint labels Newly collected advisory2 linked entries across history · in Security Follow evidence and connection reasons
- Elo: Sandbox escape to arbitrary Node.js / browser code execution via unfiltered `.constructor` member access in Elo JavaScript emitter Newly collected advisory2 linked entries across history · in Security Follow evidence and connection reasons
- coredump: hold RCU while releasing parked threads Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- ftrace: Initialize modname and offset in print_rec() Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- asymmetric_keys: reject trust keys without IDs Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- keys/trusted_keys: return immediately after TPM unseal failure Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- keys: Protect the read method check against type removal Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- keys: make keyring indexes independent of kernel addresses Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- keys: Protect the type name while describing a key Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- keys: Check the authorization payload in process keyring searches Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- keys: Avoid the owner account dereference in named keyring lookup Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- io_uring/waitid: prevent cancel reference wrap Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- tracing/syscalls: Use copy_from_user for the faultable syscall buffer Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- tracing/histograms: Verify event_call identity when updating synth_event refcount Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- tracing: Unregister field variable histograms when the command fails Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- tracing: Save the event file instead of the compatible histogram Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- tracing: Reject incomplete event filter expressions Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- tracing: Hold trace_types_lock when resetting last boot data from readers Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- tracing: Hold trace_types_lock when updating modules in persistent instances Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons
- Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn Affected-version evidence changed2 linked entries across history · in Security Follow evidence and connection reasons