-
CVE-2026-97790
•
published on October 13, 2026
Improper link resolution before file access ('link following') in Windows Container Isolation FS Filter Driver (unionfs.sys) allows an authorized attacker to perform tampering locally.
-
CVE-2026-97779
•
published on October 13, 2026
Out-of-bounds read in Microsoft Office Excel allows an unauthorized attacker to disclose information over a network.
-
CVE-2026-97778
•
published on October 13, 2026
Integer overflow or wraparound in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97773
•
published on October 13, 2026
Heap-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97768
•
published on October 13, 2026
Heap-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97764
•
published on September 25, 2026
django-allauth before 65.19.4 does not have the expected limits on failed login attempts because, in some common configurations, an attacker can leverage the handling of diacritics (e.g., accents) for a higher effective limit.
-
CVE-2026-97761
•
published on October 13, 2026
Stack-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97760
•
published on October 13, 2026
Out-of-bounds read in Microsoft Office Excel allows an unauthorized attacker to disclose information over a network.
-
CVE-2026-97757
•
published on October 13, 2026
Heap-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97751
•
published on October 13, 2026
Heap-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97749
•
published on October 13, 2026
Double free in Microsoft Office Outlook allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97743
•
published on October 13, 2026
Use after free in Microsoft Office Excel allows an unauthorized attacker to disclose information over a network.
-
CVE-2026-97741
•
published on October 13, 2026
Heap-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.
-
CVE-2026-97718
•
published on November 2, 2026
CVE-2026-97718 Is a cross-site request forgery vulnerability
in version 14.60 of the Secure Access server. Because of a bypassed security control, an
attacker can cause an admin to create an account under their control.
-
CVE-2026-97716
•
published on October 7, 2026
CVE-2026-97716
is a vulnerability in the connection set up sub-system of Secure Access servers
prior to version 14.60. Unauthenticated attackers can send specially crafted
traffic to the server and cause a persistent denial of service.
-
CVE-2026-97715
•
published on October 7, 2026
CVE-2026-97715 is
a vulnerability in the client registration process of Secure Access servers
prior to version 14.60. Authenticated attackers can pass malformed data to the
server and cause a persistent denial of service.
-
CVE-2026-97714
•
published on October 7, 2026
CVE-2026-97714
is a is a vulnerability in the authentication sub-system of Secure Access
servers prior to version 14.60. Attackers can send a malformed response during
authentication and cause a persistent denial of service.
-
CVE-2026-97692
•
published on November 13, 2026
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.6, 1.5.2, and 1.6.1, the BACnet/SC message decoder walks the header-option list by following each option's MORE bit. Nothing rejects a list whose last option still has the MORE bit set, and the decode walk has no upper bound on how many options it processes. A single crafted BVLC-SC frame makes the walk advance one option past the end of the message and read message[message_len], one byte out of bounds. When the bytes after the message carry more MORE-set option markers, the walk keeps going: it runs past the fixed 4-entry option array and writes decoded option fields out of bounds. On the server that decode array is the static global bsc_dm, so the out-of-bounds write lands in adjacent BSS. Both faults are reachable before authentication, from the first frame a peer sends on a BACnet/SC connection, and the bytes that follow the message are the same peer's prior-frame data. This issue has been patched in versions 1.4.6, 1.5.2, 1.6.1, and 1.7.0.
-
CVE-2026-97689
•
published on September 29, 2026
urllib3 is an HTTP client library for Python. From 1.10.3 until 2.8.0, the HTTPResponse.read_chunked and HTTPResponse.stream methods can allocate unbounded memory because the streaming chunk parser buffers the chunk-size field until newline or EOF without a length bound. The trigger is that a malicious server returns Transfer-Encoding: chunked followed by a very long run of bytes without a newline. The attack mechanism is that a malicious HTTP server sends a very long unterminated chunk-size line. The impact is that unbounded memory allocation can exhaust the client process. This issue is fixed in version 2.8.0.
-
CVE-2026-97687
•
published on September 29, 2026
urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0.