PULSE
FEED
ransomqilin reclama a Meridian Capital Group · US · Financial 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 · Manufacturingransomqilin reclama a Meridian Capital Group · US · Financial 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 · Manufacturing
← All CVEs
CVE WatchNov 17, 2026

CVE-2026-107853

tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. From 2.1.0 until 2.2.5 for tiny-secp256k1 and from 2.2.2 until 2.2.5 for @bitcoin-js/t

CVSS

—

No CVSS

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 17, 2026 · Last modified: Nov 17, 2026 · CWE-252

EPSS · 30d

Not enough EPSS history yet.

Technical description

tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. From 2.1.0 until 2.2.5 for tiny-secp256k1 and from 2.2.2 until 2.2.5 for @bitcoin-js/tiny-secp256k1-asmjs, the three-argument xOnlyPointAddTweakCheck path ignores the backend failure return from xOnlyPointAddTweak when a tweak produces the point at infinity. The shared X_ONLY_PUBLIC_KEY_INPUT buffer then still contains the original point, so a caller-controlled resultToCheck equal to that point can make the stale-buffer comparison return true even though no tweaked key exists. Protocols that rely on this helper to validate caller-controlled internal keys, tweaks, and comparison values can accept an invalid derived key. This issue is fixed in version 2.2.5.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-198093.3 LOW
1.3%
——0The user-mode system call verifier z_vrfy_charger_get_prop() in drivers/charger/charger_handlers.c declares an uninitialized union charger_propval k_val on the kernel (privileged) stack, passes it to the charger driver back end via z_impl_charger_get_prop(), and then copies the full sizeof(union charger_propval) back into the calling user thread's buffer with k_usermode_to_copy(). That discloses kernel stack contents on two paths: On error. The copy-out ignores the driver's return code. In-tree back ends return an error without writing through the value pointer for properties they do not implement: charger_gpio_get_prop() returns -ENOTSUP unconditionally, and bq24190_get_prop() has a default: return -ENOTSUP; arm that never touches val. The whole union is then stack residue. On success. A back end writes only the one union member the requested property selects (for example sbs_charger.c writes the one-byte val->present for CHARGER_PROP_PRESENT and returns 0), yet the handler still copies the whole union, so every byte beyond that member is uninitialized. The handler is compiled only when CONFIG_USERSPACE=y and is reachable by any user-mode thread that has been granted access to a charger device object. K_SYSCALL_DRIVER_CHARGER() validates only the device object and its API pointer, not the property identifier, so an unprivileged thread can choose prop freely: an unimplemented property forces the error path, a narrow one the success path, and the call can be repeated at will. Each call discloses up to the size of the union (12 bytes on a 32-bit target, 16 bytes on 64-bit targets where the function-pointer members widen it) of supervisor-stack memory. The bytes are residue of earlier kernel-side frames on the thread's privileged stack and can contain kernel object addresses and saved return addresses, which an unprivileged thread cannot otherwise observe and which help defeat address-layout assumptions when exploiting a separate memory-safety defect. There is no integrity or availability impact. Two commits fix it, and both are needed. 5054384e983c skips the copy-out when the back end reports an error. c31cac727d02 zeroes the union before the driver call, so the bytes copied out on success are driver-written data or zeros. A tree carrying only the first still leaks on every successful call.13h
CVE-2026-62930—
6.7%
——2Unchecked return value in the MigTD's TLS implementation for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow a denial of service. Network adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via adjacent access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.1d
CVE-2026-62920—
1.9%
——1Unchecked return value in the MigTD error handling for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow a denial of service. System software adversary with a privileged user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.1d
CVE-2026-1252255.5 MED
7.9%
——2FFmpeg through 9.0.2 contains a NULL pointer dereference vulnerability in aac_adtstoasc_filter() that allows attackers to crash applications via oversized ADTS AAC packets. Attackers can supply a crafted file with a packet over 256 MB, overflowing the bit count so init_get_bits() fails unchecked and get_bits() crashes during MP4, Matroska, FLV or LATM remuxing.7d
CVE-2026-1251745.5 MED
7.9%
——2FFmpeg before 8.1.3 and 9.x before 9.0.2 contains a NULL pointer dereference vulnerability in ff_hap_set_chunk_count() in libavcodec/hap.c, where a shadowed return variable masks reallocation failures. Attackers can supply a crafted Hap video frame with an oversized chunk count so the decoder writes through a NULL chunk table, crashing the application.7d
CVE-2026-1250724.7 MED
6.6%
——2FFmpeg through 9.0.2 contains a NULL pointer dereference vulnerability in mp_decode_frame() in libavcodec/mpegaudiodec_template.c because init_get_bits() failure is ignored after a signed integer overflow. Attackers can pass an oversized packet to the mp3adu decoder through the libavcodec API, causing reads through a NULL buffer that crash the process.7d