https://github.com/zakkanijia/POC/blob/main/giflib/giftool/giflib_giftool_gce_len_heap_oobwrite_disclosure.md reports:

Buffer Overflow vulnerability in giflib v.5.2.2 allows a remote attacker to cause a denial of service via the EGifGCBToExtension overwriting an existing Graphic Control Extension block without validating its allocated size.

The SRT project reports:

• CVE-2026-55869: Heap-Based Buffer Overflow in KMREQ Handling. A remote attacker may be able to trigger a heap-based buffer overflow during key material request processing, leading to a denial of service or potentially arbitrary code execution.
• CVE-2026-55868: Encryption State Machine Downgrade. A flaw in the encryption state machine may allow an attacker to downgrade the negotiated encryption, weakening confidentiality protections for the SRT stream.

The Weechat project reports:

Write of logger file outside of configured path.

Authentication bypass in Relay plugin, protocols "api" and "weechat".

Mailpit author reports:

Mailpit's SMTP DATA reader enforces the configured MaxMessageSize only after bufio.Reader.ReadBytes('\n') has already buffered a complete DATA line. A remote unauthenticated SMTP client can send one line larger than the configured message-size cap and force memory allocation before Mailpit returns the expected 552 5.3.4 rejection, leaving patched versions still exposed to a single-line incomplete-fix variant of the earlier SMTP DATA body-size issue.

Tailscale team reports:

Tailscale SSH Unix socket forwarding respects symlink permissions. This fix addresses a security vulnerability described in TS-2026-004.

Tailscale Serve Unix socket proxy targets are restricted to the root user. This fix addresses a security vulnerability described in TS-2026-005.

Tailscale SSH does not allow the use of UIDs or numeric-only usernames. This fix addresses a security vulnerability described in TS-2026-006.

Nodes advertising Tailscale Services filter and reject packets from service IPs on ports they do not advertise. This fix addresses a security vulnerability described in TS-2026-007.

Tailscale Serve and Tailscale Funnel terminate path walks for non-absolute paths, preventing CPU core pinning. This fix addresses a security vulnerability described in TS-2026-008.

Tailscale SSH does not allow the use of usernames with leading dashes. This fix addresses a security vulnerability described in TS-2026-009.

The traefik project releases a new version addressing multiple vulnerabilities:

• GHSA-cxjq-mrr5-89rv (Authentication Bypass via Path Traversal in ReplacePathRegex Middleware)
• GHSA-42cj-m3vj-89wv (CRD IngressRouteTCP ServersTransport Cross-Provider Namespace Bypass)
• GHSA-qq9q-x9w4-chhj (Gateway API HTTPRoute BackendRef ExtensionRef Namespace Confusion)

• GHSA-8rxv-jg7p-wvg3 (Kubernetes Ingress NGINX RewriteTarget Path Traversal Allows Route-Level Authentication Bypass)

phpMyFAQ team reports:

An authenticated administrator can supply an untrusted update-package path to the configuration API, causing phpMyFAQ to write an arbitrary PHP file to the server and thereby execute attacker-controlled code.

An attacker can exploit a path traversal in the category image deletion routine to remove arbitrary files outside the intended directory, which can leave the installation in a state that allows a setup takeover.

The two-factor authentication login flow can be completed without verifying the password factor, so an attacker who possesses only the second factor is able to authenticate as the victim.

A delegated administrator with only the GROUP_EDIT permission can assign group memberships without restriction through GroupController::updateMembers, inheriting rights they do not hold and escalating their privileges.

An authenticated user can inject SQL through an unescaped stop word inserted via StopWords::add(), allowing manipulation of the underlying database query.

The nginx development team reports:

Buffer overflow when using map and regex (CVE-2026-42533). Severity: major.

Memory disclosure when using ngx_http_slice_module (CVE-2026-60005). Severity: medium.

Use-after-free when using ngx_http_ssi_module (CVE-2026-56434). Severity: medium.

The OpenQuantumSafe project reports:

• uninitialized encaps_derand pointer dereference
• out-of-bounds read in XMSS/XMSS^MT signature verification
• Integer underflow in CROSS crypto_sign_open()
• incorrect array size when calling secure_clean
• Implemented optimization barrier OQS_MEM_BLACK_BOX and applied to ct_select in FrodoKEM

https://access.redhat.com/errata/RHSA-2026:24984 reports:

A flaw was found in Poppler's Splash backend. A remote attacker could exploit this vulnerability by crafting a malicious PDF file that, when rendered, triggers an integer overflow in the `tilingPatternFill` function. This overflow leads to an undersized heap memory allocation, allowing a subsequent out-of-bounds write. Successful exploitation could result in arbitrary code execution, information disclosure, or denial of service within the context of the application processing the PDF.

The OCaml Team reports:

Installing files through .install files do not check symlinks resolution of the target path, and so can bypass sandboxing.

Credits:
Reporter: "Kate Deplaix"
Remediation Developer: "Nathan Rebours"
Remediation Reviewer: "Raja Boujbel"
Coordinator: "Hannes Mehnert"

Apache Software Foundation reports:

Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution.

MITRE reports:

Apache Commons HttpClient 3.x, as used in ..., does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

Mailpit author reports:

Mailpit's SMTP server reads each command line with an unbounded bufio.Reader.ReadString('\n') before parsing the command or enforcing any protocol length limit. A remote SMTP client can send an oversized single command line and force Mailpit to allocate attacker-controlled memory before the server returns a syntax error or times out, even though RFC 5321 limits SMTP command lines to 512 octets including CRLF.

Mailpit's thumbnail endpoint decodes attacker-supplied image attachments into a full raster before checking any decoded-pixel, dimension, or memory budget. A remote client that can store an email and reach the default web API can supply a compact high-dimension image, then request /api/v1/message/{id}/part/{partID}/thumb to force server-side memory and CPU work far larger than the encoded attachment size before Mailpit returns a 180x120 thumbnail.

Gitlab reports:

Cross-site Scripting issue in vulnerability evidence table renderer impacts GitLab EE

HTML Injection in wiki markup rendering impacts GitLab CE/EE

Insufficiently Protected Credentials issue in repository mirroring impacts GitLab EE

Improper Access Control issue in work items impacts GitLab EE

Missing Authorization issue in commit discussion display impacts GitLab CE/EE

Ambiguity Reference issue in a tag or branch impacts GitLab CE/EE

Incorrect Authorization issue in group-level settings impacts GitLab EE

Incorrect Authorization issue in compliance violation management impacts GitLab EE

X.Org project reports:

Multiple issues have been found in the libXfont2 library published by X.Org for which we are releasing security fixes in libXfont2-2.0.8.

X.Org project reports:

Multiple issues have been found in the X server and Xwayland implementations published by X.Org for which we are releasing security fixes for in xorg-server-21.1.24 and xwayland-24.1.13.

X.Org project reports:

Multiple issues have been found in the X server and Xwayland implementations published by X.Org for which we are releasing security fixes for in xorg-server-21.1.24 and xwayland-24.1.13.

Cacti project reports:

This release includes fixes for a number of vulnerabilities that were responsibly disclosed by external researchers

• CVE-2026-39894 RRDtool metric shift via LC_NUMERIC locale comma decimal formatting
• CVE-2026-40082 Session Fixation via missing session_regenerate_id() after login
• CVE-2026-40941 Package Import Signature Validation Bypass allows self-signed packages
• CVE-2026-39897 Reflected XSS in html_auth_footer error message output
• CVE-2026-39900 Reflected XSS via tab parameter in auth_profile.php JavaScript context
• CVE-2026-46531 SQL Injection in automation_tree_rules.php
• CVE-2026-44481 Pre-auth Open Redirect via link.php Referer header
• CVE-2026-39952 Stored XSS in Report Tree expansion titles
• CVE-2026-39893 Pre-authentication SQL injection via rfilter RLIKE clause in graph_view.php
• CVE-2026-22802 Authentication Bypass leads to information disclosure
• CVE-2026-40080 Open Redirect via HTTP_REFERER substring check in auth_login_redirect
• CVE-2026-40078 Backend ORDER BY SQL Injection
• CVE-2026-39949 Authenticated Remote Code Execution via Host Variable Injection
• CVE-2026-40081 Reports IDOR allows any authenticated user to modify other users' reports (CWE-639)
• CVE-2026-39948 SQL Injection via rfilter parameter in RLIKE clauses
• CVE-2026-39902 Authenticated RCE on Data Input
• CVE-2026-39898 Reflected XSS via rfilter parameter in aggregate_graphs.php input value
• CVE-2026-41884 Arbitrary File Read via Reports format_file path traversal
• CVE-2026-39955 Pre-Authentication SQL Injection via unanchored FILTER_VALIDATE_REGEXP in graph_view.php
• CVE-2026-39896 TOCTOU race in auth_process_lockout allows brute-force lockout bypass
• CVE-2026-39950 Arbitrary PHP file write via Plugin Archive extraction leading to RCE
• CVE-2026-40083 SQL Injection in managers.php via uncast array values in IN clauses
• CVE-2026-40084 Arbitrary File Read via path traversal in Report format_file parameter
• CVE-2026-39951 Stored SQL Injection via graph_name_regexp in Reports feature
• CVE-2026-39899 Path traversal via filename parameter in package_import.php
• CVE-2026-39938 Unauthenticated LFI via graph_theme and rrdtool IPC serialization hardening
• CVE-2026-39939 Path traversal in Package Import file write allows arbitrary file creation in webroot
• CVE-2026-39947 RRDtool IPC pipe poisoning via is_numeric newline bypass in rrdtool_function_update
• CVE-2026-39895 Second-order RCE via unescaped log path in exec_background shell redirection
• CVE-2026-40079 Command Injection via escape_command() no-op in RRDtool execution
• CVE-2026-40194, CVE-2026-32935 in phpseclib - This is breaking change for RRDProxy
• CVE-2026-1513 billboard.js before 3.18.0 Improper Input Sanitization Allows Remote JavaScript Execution

xrdp projects reports:

xrdp v0.10.6.1 fixes 10 vulnerabilities and 1 regression introduced by a vulnerability fix in the previous release.

Tim Wojtulewicz of Corelight reports:

The NVT, Rlogin, and RSH analyzers have received fixes to avoid unbounded state growth. Due to the fact that these packets can be received from remote hosts, these are considered DoS risks.

A specially crafted WebSocket payload can cause the Spicy WebSocket analyzer to use excessive memory when processing close, ping, and pong frames. Due to the fact that these packets can be received from remote hosts, these are considered a DoS risk.

A specially crafted series of Finger packets can cause the Spicy Finger analyzer to use excessive amounts of memory and potentially crash Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk.

A specially crafted Kerberos packet can cause the Kerberos analyzer to enter an invalid state and potentially crash Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk.

A specially crafted series of RDP packets can cause the RDP analyzer to use excessive amounts of memory and potentially crash Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk.

A specially crafted IP packet can cause the IP analyzer to read past the end of the contents of the packet when emitting the packet_contents event and possibly crash. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk.

A specially crafted IP packet can cause the packet discarding code to read off the end of the packet when looking for follow-on header data. This may potentially lead to a crash of Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk.

A specially crafted series of Gnutella packets may cause Zeek to continue accumulating memory and eventually crash. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk.

A specially crafted ICMPv6 packet can cause the ICMP analyzer to skip part of the packet and not report corresponding events and logs. Due to the fact that these packets can be received from remote hosts, this is considered an evasion risk.

A specially crafted SSH packet can cause the SSH analyzer to throw BinPAC exceptions for extremely large packets and skip logging them otherwise. Due to the fact that these packets can be received from remote hosts, this is considered an evasion risk.

A number of issues with the HTTP analyzer were found involving unusual Content-Length, Transfer-Encoding and Expect header usage. Due to the fact that these packets can be received from remote hosts, this is considered an evasion risk.

A series of fixes were applied to the serialization code in Zeek to avoid buffer overreads with both Broker and ZeroMQ traffic. On debug builds, these hit various abort() conditions and cause Zeek to exit. Due to the fact that all of these states require direct access to the Broker/ZeroMQ ports (meaning access to the local network to some degree), this isn’t considered a DoS risk.

Problem Description

When GNU Emacs renders an SVG image whose image spec includes a :css property, an off-by-one error in svg_load_image() writes a NUL byte one position past the end of a heap allocation. The copied string is also left without NUL termination within its allocation, causing a subsequent out-of-bounds read.

Impact

A single NUL byte heap overflow is a well-understood exploitation primitive ("poison NUL byte") that can corrupt heap metadata and potentially be escalated to arbitrary code execution. The overflow can be triggered by Lisp code that displays an SVG image with a crafted :css property.

The Weechat project reports:

Pre-auth memory leak in relay-api POST /api/handshake (unfreed JSON body) → unauthenticated remote memory-exhaustion DoS.

The Rouncube project reports:

See links for more detail

The traefik project releases a new version addressing multiple CVEs:

• CVE-2026-54763 (underscore-variant identity spoofing)
• CVE-2026-54764 (ForwardAuth middleware leaks X-Forwarded-Port spoofing)
• CVE-2026-54765 (Gateway HTTPRoute backendRef filters can leak backend context)

CGI-Session project reports:

SECURITY: Strengthen cryptographic randomness of MD5 driver.

Chrome Releases reports:

This update includes 382 security fixes:

• [506558270] Critical CVE-2026-13774: Use after free in Extensions.
• [511766407] Critical CVE-2026-13775: Use after free in GPU.
• [513012139] Critical CVE-2026-13776: Type Confusion in Dawn.
• [513128566] Critical CVE-2026-13777: Insufficient validation of untrusted input in iOSWeb.
• [513167952] Critical CVE-2026-13778: Use after free in WebUSB.
• [513222854] Critical CVE-2026-13779: Use after free in Chromoting.
• [514769383] Critical CVE-2026-13780: Insufficient validation of untrusted input in ANGLE.
• [516457532] Critical CVE-2026-13781: Insufficient validation of untrusted input in Skia.
• [516683433] Critical CVE-2026-13782: Use after free in Browser.
• [516962178] Critical CVE-2026-13783: Use after free in Views.
• [516962715] Critical CVE-2026-13784: Use after free in Views.
• [517021684] Critical CVE-2026-13785: Use after free in Bluetooth.
• [518007821] Critical CVE-2026-13786: Use after free in Ozone.
• [522919313] Critical CVE-2026-13787: Use after free in Chromoting.
• [523119897] Critical CVE-2026-13788: Use after free in Fullscreen.
• [493847920] High CVE-2026-13789: Use after free in GPU.
• [457771782] High CVE-2026-13790: Side-channel information leakage in Scroll.
• [503850012] High CVE-2026-13791: Insufficient validation of untrusted input in Downloads.
• [496012368] High CVE-2026-13792: Use after free in Touchbar.
• [510829679] High CVE-2026-13793: Insufficient policy enforcement in SVG.
• [513893425] High CVE-2026-13794: Insufficient validation of untrusted input in WebAppInstalls.
• [476591032] High CVE-2026-13795: Insufficient policy enforcement in Chrome for iOS.
• [491894115] High CVE-2026-13796: Integer overflow in Chromecast.
• [499025645] High CVE-2026-13797: Insufficient validation of untrusted input in Chromecast.
• [499048914] High CVE-2026-13798: Heap buffer overflow in Chromecast.
• [499252371] High CVE-2026-13799: Use after free in QUIC.
• [500108770] High CVE-2026-13800: Inappropriate implementation in Updater.
• [500587568] High CVE-2026-13801: Integer overflow in Chromecast.
• [501623322] High CVE-2026-13802: Use after free in Views.
• [501669642] High CVE-2026-13803: Type Confusion in Chrome Tabs.
• [501873032] High CVE-2026-13804: Use after free in Chromecast.
• [502282040] High CVE-2026-13805: Use after free in GFX.
• [503333798] High CVE-2026-13806: Insufficient validation of untrusted input in Accessibility.
• [504194494] High CVE-2026-13807: Use after free in Import.
• [504221510] High CVE-2026-13808: Insufficient data validation in Chrome for iOS.
• [504222227] High CVE-2026-13809: Side-channel information leakage in Safe Browsing. eported by Google on 2026-04-19
• [504600482] High CVE-2026-13810: Inappropriate implementation in Input.
• [506149253] High CVE-2026-13811: Use after free in IME.
• [508293203] High CVE-2026-13812: Insufficient validation of untrusted input in Chrome for iOS.
• [508462149] High CVE-2026-13813: Insufficient validation of untrusted input in Chrome for iOS.
• [511712766] High CVE-2026-13814: Use after free in Views.
• [511722207] High CVE-2026-13815: Use after free in Blink.
• [511735715] High CVE-2026-13816: Insufficient validation of untrusted input in File Input.
• [511739631] High CVE-2026-13817: Insufficient validation of untrusted input in Glic.
• [511823182] High CVE-2026-13818: Inappropriate implementation in Passwords.
• [512962749] High CVE-2026-13819: Out of bounds read in ANGLE.
• [512986879] High CVE-2026-13820: Out of bounds read in Skia.
• [513142445] High CVE-2026-13821: Use after free in Canvas.
• [513148038] High CVE-2026-13822: Inappropriate implementation in Extensions.
• [513163011] High CVE-2026-13823: Use after free in Glic.
• [513177497] High CVE-2026-13824: Insufficient validation of untrusted input in Extensions.
• [513209610] High CVE-2026-13825: Uninitialized Use in Dawn.
• [513237800] High CVE-2026-13826: Inappropriate implementation in Autofill.
• [513371963] High CVE-2026-13827: Use after free in Updater.
• [513399832] High CVE-2026-13828: Inappropriate implementation in Enterprise.
• [513490996] High CVE-2026-13829: Insufficient validation of untrusted input in Settings.
• [513727494] High CVE-2026-13830: Use after free in Chromoting.
• [513781328] High CVE-2026-13831: Use after free in GPU.
• [513822378] High CVE-2026-13832: Use after free in Headless.
• [513920082] High CVE-2026-13833: Uninitialized Use in ANGLE.
• [513925114] High CVE-2026-13834: Insufficient validation of untrusted input in ANGLE.
• [514338102] High CVE-2026-13835: Inappropriate implementation in XML.
• [514420555] High CVE-2026-13836: Inappropriate implementation in CSS.
• [514429130] High CVE-2026-13837: Inappropriate implementation in CSS.
• [514445398] High CVE-2026-13838: Inappropriate implementation in CSS.
• [514449396] High CVE-2026-13839: Inappropriate implementation in CSS.
• [514609778] High CVE-2026-13840: Insufficient policy enforcement in Canvas.
• [515467789] High CVE-2026-13841: Integer overflow in Skia.
• [516836297] High CVE-2026-13842: Incorrect security UI in Chrome for iOS.
• [516869032] High CVE-2026-13843: Insufficient validation of untrusted input in Chrome for iOS.
• [516926115] High CVE-2026-13844: Use after free in Updater.
• [516936863] High CVE-2026-13845: Use after free in DOM.
• [516999424] High CVE-2026-13846: Use after free in USB.
• [517073397] High CVE-2026-13847: Insufficient validation of untrusted input in Chrome for iOS.
• [517345069] High CVE-2026-13848: Use after free in Forms.
• [517351411] High CVE-2026-13849: Insufficient validation of untrusted input in Chromoting.
• [517610676] High CVE-2026-13850: Insufficient validation of untrusted input in Chrome for iOS.
• [519692255] High CVE-2026-13851: Insufficient validation of untrusted input in WebAppInstalls.
• [522560124] High CVE-2026-13852: Insufficient validation of untrusted input in WebAppInstalls.
• [523224019] High CVE-2026-13853: Use after free in Journeys.
• [523690961] High CVE-2026-13854: Use after free in Ozone.
• [524395469] High CVE-2026-13855: Use after free in Ozone.
• [508092634] Medium CVE-2026-13856: Insufficient validation of untrusted input in Speech.
• [479203484] Medium CVE-2026-13857: Inappropriate implementation in Geometry.
• [507090179] Medium CVE-2026-13858: Out of bounds read in FFmpeg.
• [484756087] Medium CVE-2026-13859: Inappropriate implementation in ANGLE.
• [417052041] Medium CVE-2026-13860: Incorrect security UI in Autofill.
• [495456765] Medium CVE-2026-13861: Use after free in Core.
• [495897416] Medium CVE-2026-13862: Insufficient policy enforcement in Web Authentication (Passkeys & Security Keys).
• [496012495] Medium CVE-2026-13863: Insufficient validation of untrusted input in CustomTabs.
• [496399913] Medium CVE-2026-13864: Insufficient policy enforcement in WebHID.
• [497090912] Medium CVE-2026-13865: Insufficient validation of untrusted input in Enterprise.
• [497207698] Medium CVE-2026-13866: Insufficient validation of untrusted input in Input.
• [497345177] Medium CVE-2026-13867: Inappropriate implementation in Geolocation.
• [497453475] Medium CVE-2026-13868: Inappropriate implementation in Network.
• [497610642] Medium CVE-2026-13869: Use after free in Device.
• [497634837] Medium CVE-2026-13870: Use after free in WebView.
• [497961376] Medium CVE-2026-13871: Insufficient data validation in GuestView.
• [497977983] Medium CVE-2026-13872: Insufficient validation of untrusted input in WebAppInstalls.
• [498085466] Medium CVE-2026-13873: Out of bounds memory access in Layout.
• [498411773] Medium CVE-2026-13874: Inappropriate implementation in DataTransfer.
• [498721671] Medium CVE-2026-13875: Insufficient validation of untrusted input in GPU.
• [498722200] Medium CVE-2026-13876: Inappropriate implementation in Network.
• [498820206] Medium CVE-2026-13877: Insufficient validation of untrusted input in ANGLE.
• [499007266] Medium CVE-2026-13878: Use after free in Bluetooth.
• [499022239] Medium CVE-2026-13879: Use after free in Bluetooth.
• [499025880] Medium CVE-2026-13880: Use after free in USB.
• [499100491] Medium CVE-2026-13881: Insufficient data validation in WebAppInstalls.
• [499162550] Medium CVE-2026-13882: Inappropriate implementation in USB.
• [500030250] Medium CVE-2026-13883: Type Confusion in ANGLE.
• [500077014] Medium CVE-2026-13884: Heap buffer overflow in Chromecast.
• [500474409] Medium CVE-2026-13885: Use after free in Skia.
• [500475136] Medium CVE-2026-13886: Policy bypass in Isolated Web Apps.
• [500508524] Medium CVE-2026-13887: Insufficient policy enforcement in NFC.
• [500566906] Medium CVE-2026-13888: Use after free in Extensions.
• [500588580] Medium CVE-2026-13889: Insufficient validation of untrusted input in WebAuthentication.
• [500601345] Medium CVE-2026-13890: Out of bounds read in Chromecast.
• [501631475] Medium CVE-2026-13891: Insufficient validation of untrusted input in Extensions.
• [501674841] Medium CVE-2026-13892: Inappropriate implementation in Chrome for iOS.
• [501729582] Medium CVE-2026-13893: Insufficient validation of untrusted input in WebUI.
• [501741117] Medium CVE-2026-13894: Insufficient policy enforcement in Network.
• [501770542] Medium CVE-2026-13895: Inappropriate implementation in Autofill.
• [501820076] Medium CVE-2026-13896: Insufficient policy enforcement in Glic.
• [501877896] Medium CVE-2026-13897: Insufficient policy enforcement in Chromecast.
• [501925480] Medium CVE-2026-13898: Use after free in Cast Receiver.
• [502109002] Medium CVE-2026-13899: Use after free in HTML.
• [502374993] Medium CVE-2026-13900: Insufficient validation of untrusted input in Chromecast.
• [503585173] Medium CVE-2026-13901: Insufficient validation of untrusted input in Serial.
• [503725717] Medium CVE-2026-13902: Inappropriate implementation in Chrome for iOS.
• [503912196] Medium CVE-2026-13903: Insufficient policy enforcement in Bluetooth.
• [504185807] Medium CVE-2026-13904: Incorrect security UI in Safe Browsing.
• [504192688] Medium CVE-2026-13905: Incorrect security UI in Chrome for iOS.
• [504613867] Medium CVE-2026-13906: Out of bounds read in Codecs.
• [505156685] Medium CVE-2026-13907: Inappropriate implementation in iOSWeb.
• [505242189] Medium CVE-2026-13908: Insufficient validation of untrusted input in Omnibox.
• [505933538] Medium CVE-2026-13909: Insufficient policy enforcement in DevTools.
• [507231605] Medium CVE-2026-13910: Insufficient policy enforcement in WebXR.
• [507239830] Medium CVE-2026-13911: Insufficient data validation in Spellcheck.
• [508259433] Medium CVE-2026-13912: Incorrect security UI in Safe Browsing.
• [508260619] Medium CVE-2026-13913: Insufficient policy enforcement in Autofill.
• [508273690] Medium CVE-2026-13914: Inappropriate implementation in Passwords.
• [508275293] Medium CVE-2026-13915: Use after free in Chrome for iOS.
• [508283108] Medium CVE-2026-13916: Inappropriate implementation in Chrome for iOS.
• [508286935] Medium CVE-2026-13917: Insufficient validation of untrusted input in Chrome for iOS.
• [509712284] Medium CVE-2026-13918: Use after free in Chrome for iOS.
• [511249430] Medium CVE-2026-13919: Insufficient data validation in Extensions.
• [511722559] Medium CVE-2026-13920: Insufficient validation of untrusted input in Media.
• [511738175] Medium CVE-2026-13921: Insufficient validation of untrusted input in DeviceBoundSessionCredentials.
• [511748106] Medium CVE-2026-13922: Side-channel information leakage in Paint.
• [511772034] Medium CVE-2026-13923: Uninitialized Use in GPU.
• [511784747] Medium CVE-2026-13924: Insufficient validation of untrusted input in WebView.
• [511802911] Medium CVE-2026-13925: Inappropriate implementation in Downloads.
• [511814550] Medium CVE-2026-13926: Insufficient validation of untrusted input in Network.
• [511826446] Medium CVE-2026-13927: Insufficient validation of untrusted input in UI.
• [512162479] Medium CVE-2026-13928: Insufficient validation of untrusted input in Enterprise.
• [512249559] Medium CVE-2026-13929: Insufficient validation of untrusted input in DevTools.
• [512937764] Medium CVE-2026-13930: Insufficient policy enforcement in Actor.
• [512997441] Medium CVE-2026-13931: Inappropriate implementation in Media.
• [513001690] Medium CVE-2026-13932: Inappropriate implementation in Sharing.
• [513002625] Medium CVE-2026-13933: Insufficient policy enforcement in Passwords.
• [513006636] Medium CVE-2026-13934: Insufficient validation of untrusted input in Dawn.
• [513009005] Medium CVE-2026-13935: Side-channel information leakage in ComputePressure.
• [513044658] Medium CVE-2026-13936: Inappropriate implementation in Passwords.
• [513046494] Medium CVE-2026-13937: Insufficient policy enforcement in Passwords.
• [513143921] Medium CVE-2026-13938: Integer overflow in Fonts.
• [513149760] Medium CVE-2026-13939: Insufficient validation of untrusted input in WebShare.
• [513158425] Medium CVE-2026-13940: Uninitialized Use in Cast.
• [513183855] Medium CVE-2026-13941: Inappropriate implementation in SiteSettings.
• [513186670] Medium CVE-2026-13942: Insufficient validation of untrusted input in Video Capture.
• [513204116] Medium CVE-2026-13943: Uninitialized Use in CSS.
• [513224212] Medium CVE-2026-13944: Inappropriate implementation in DataTransfer.
• [513226551] Medium CVE-2026-13945: Insufficient policy enforcement in Extensions.
• [513274039] Medium CVE-2026-13946: Inappropriate implementation in ScriptInjections.
• [513280648] Medium CVE-2026-13947: Uninitialized Use in XR.
• [513286820] Medium CVE-2026-13948: Insufficient policy enforcement in Extensions.
• [513311569] Medium CVE-2026-13949: Insufficient policy enforcement in Payments.
• [513360781] Medium CVE-2026-13950: Uninitialized Use in GPU.
• [513394321] Medium CVE-2026-13951: Policy bypass in USB.
• [513401808] Medium CVE-2026-13952: Inappropriate implementation in PerformanceAPIs.
• [513459192] Medium CVE-2026-13953: Inappropriate implementation in SplitView.
• [513504934] Medium CVE-2026-13954: Insufficient policy enforcement in XML.
• [513508305] Medium CVE-2026-13955: Insufficient validation of untrusted input in CustomTabs.
• [513515168] Medium CVE-2026-13956: Incorrect security UI in PageInfo.
• [513553557] Medium CVE-2026-13957: Incorrect security UI in Extensions.
• [513567306] Medium CVE-2026-13958: Uninitialized Use in Codecs.
• [513609249] Medium CVE-2026-13959: Insufficient validation of untrusted input in Blink.
• [513714023] Medium CVE-2026-13960: Inappropriate implementation in Passwords.
• [513719481] Medium CVE-2026-13961: Insufficient validation of untrusted input in DevTools.
• [513721370] Medium CVE-2026-13962: Insufficient data validation in PDF.
• [513727626] Medium CVE-2026-13963: Inappropriate implementation in DevTools.
• [513735096] Medium CVE-2026-13964: Insufficient policy enforcement in WebView.
• [513737952] Medium CVE-2026-13965: Use after free in Oilpan.
• [513741393] Medium CVE-2026-13966: Inappropriate implementation in History.
• [513751951] Medium CVE-2026-13967: Type Confusion in V8.
• [513762145] Medium CVE-2026-13968: Insufficient validation of untrusted input in DevTools.
• [513762962] Medium CVE-2026-13969: Uninitialized Use in UI.
• [513779283] Medium CVE-2026-13970: Uninitialized Use in Media.
• [513780208] Medium CVE-2026-13971: Uninitialized Use in Skia.
• [513792140] Medium CVE-2026-13972: Inappropriate implementation in Paint.
• [513832989] Medium CVE-2026-13973: Inappropriate implementation in UI.
• [513850475] Medium CVE-2026-13974: Integer overflow in Safe Browsing.
• [513857658] Medium CVE-2026-13975: Out of bounds read in ANGLE.
• [513858286] Medium CVE-2026-13976: Heap buffer overflow in Storage.
• [513859894] Medium CVE-2026-13977: Inappropriate implementation in HTMLParser.
• [513866949] Medium CVE-2026-13978: Insufficient policy enforcement in PageInfo.
• [513988889] Medium CVE-2026-13979: Inappropriate implementation in Paint.
• [513989973] Medium CVE-2026-13980: Incorrect security UI in Chrome for iOS.
• [513990408] Medium CVE-2026-13981: Inappropriate implementation in Chrome for iOS.
• [514006829] Medium CVE-2026-13982: Incorrect security UI in Passwords.
• [514009910] Medium CVE-2026-13983: Incorrect security UI in Chrome for iOS.
• [514010404] Medium CVE-2026-13984: Incorrect security UI in TabStrip.
• [514013849] Medium CVE-2026-13985: Inappropriate implementation in MediaCapture.
• [514020959] Medium CVE-2026-13986: Inappropriate implementation in Media UI.
• [514039122] Medium CVE-2026-13987: Incorrect security UI in Mobile.
• [514040614] Medium CVE-2026-13988: Inappropriate implementation in Paint.
• [514056221] Medium CVE-2026-13989: Insufficient policy enforcement in PageInfo.
• [514058439] Medium CVE-2026-13990: Insufficient validation of untrusted input in DataTransfer.
• [514061117] Medium CVE-2026-13991: Insufficient validation of untrusted input in Chrome for iOS.
• [514063409] Medium CVE-2026-13992: Inappropriate implementation in UI.
• [514064139] Medium CVE-2026-13993: Incorrect security UI in WebAppInstalls.
• [514067416] Medium CVE-2026-13994: Inappropriate implementation in Credential Management.
• [514067524] Medium CVE-2026-13995: Insufficient validation of untrusted input in Autofill.
• [514068972] Medium CVE-2026-13996: Incorrect security UI in Permissions.
• [514069689] Medium CVE-2026-13997: Incorrect security UI in Extensions.
• [514070501] Medium CVE-2026-13998: Incorrect security UI in File Input.
• [514071697] Medium CVE-2026-13999: Inappropriate implementation in Extensions.
• [514461552] Medium CVE-2026-14000: Inappropriate implementation in XML.
• [514481943] Medium CVE-2026-14001: Inappropriate implementation in Network.
• [514489361] Medium CVE-2026-14002: Inappropriate implementation in Geolocation.
• [514503077] Medium CVE-2026-14003: Insufficient policy enforcement in Extensions.
• [514538751] Medium CVE-2026-14004: Inappropriate implementation in CSS.
• [514740273] Medium CVE-2026-14005: Use after free in Omnibox.
• [515423596] Medium CVE-2026-14006: Use after free in Navigation.
• [516425999] Medium CVE-2026-14007: Insufficient policy enforcement in PermissionsPolicy.
• [516781007] Medium CVE-2026-14008: Uninitialized Use in WebXR.
• [516819850] Medium CVE-2026-14009: Insufficient data validation in Passwords.
• [516924151] Medium CVE-2026-14010: Uninitialized Use in Codecs.
• [516944556] Medium CVE-2026-14011: Out of bounds read in SurfaceCapture.
• [517110749] Medium CVE-2026-14012: Side-channel information leakage in CSS.
• [517114175] Medium CVE-2026-14013: Inappropriate implementation in SVG.
• [517155893] Medium CVE-2026-14014: Inappropriate implementation in Paint.
• [517207235] Medium CVE-2026-14015: Inappropriate implementation in WebRTC.
• [517234388] Medium CVE-2026-14016: Insufficient policy enforcement in SVG.
• [517241992] Medium CVE-2026-14017: Inappropriate implementation in Navigation.
• [517350251] Medium CVE-2026-14018: Use after free in Updater.
• [517455455] Medium CVE-2026-14019: Inappropriate implementation in Passwords.
• [517598518] Medium CVE-2026-14020: Insufficient validation of untrusted input in WebXR.
• [517731924] Medium CVE-2026-14021: Insufficient validation of untrusted input in StorageAccessAPI.
• [517791835] Medium CVE-2026-14022: Insufficient validation of untrusted input in Network.
• [518063436] Medium CVE-2026-14023: Insufficient validation of untrusted input in SanitizerAPI.
• [518245882] Medium CVE-2026-14024: Use after free in Ozone.
• [506482786] Low CVE-2026-14025: Use after free in Views.
• [507263861] Low CVE-2026-14026: Incorrect security UI in SplitView.
• [361375787] Low CVE-2026-14027: Use after free in SignIn.
• [401816601] Low CVE-2026-14028: Incorrect security UI in Chrome for iOS.
• [488762971] Low CVE-2026-14030: Incorrect security UI in SplitView.
• [495459838] Low CVE-2026-14031: Incorrect security UI in File Input.
• [495783474] Low CVE-2026-14032: Use after free in Bluetooth.
• [495848160] Low CVE-2026-14033: Insufficient policy enforcement in Media.
• [496368832] Low CVE-2026-14034: Inappropriate implementation in WebXR.
• [496371586] Low CVE-2026-14035: Insufficient policy enforcement in Bluetooth.
• [496411061] Low CVE-2026-14036: Insufficient policy enforcement in Bluetooth.
• [496522611] Low CVE-2026-14037: Insufficient policy enforcement in GPU.
• [497241148] Low CVE-2026-14038: Insufficient validation of untrusted input in New Tab Page.
• [497358012] Low CVE-2026-14039: Insufficient policy enforcement in GetUserMedia.
• [497488593] Low CVE-2026-14040: Use after free in BrowserTag.
• [497544822] Low CVE-2026-14041: Insufficient policy enforcement in Serial.
• [497558336] Low CVE-2026-14042: Inappropriate implementation in Isolated Web Apps.
• [497632232] Low CVE-2026-14043: Use after free in GetUserMedia.
• [497670996] Low CVE-2026-14044: Use after free in ANGLE.
• [497723649] Low CVE-2026-14045: Insufficient validation of untrusted input in Network.
• [497959724] Low CVE-2026-14046: Inappropriate implementation in CustomTabs.
• [498864176] Low CVE-2026-14047: Insufficient policy enforcement in Extensions.
• [499189601] Low CVE-2026-14048: Use after free in Chromecast.
• [501659888] Low CVE-2026-14049: Inappropriate implementation in GPU.
• [501708647] Low CVE-2026-14050: Insufficient policy enforcement in Passwords.
• [501747804] Low CVE-2026-14051: Uninitialized Use in GamepadAPI.
• [501810874] Low CVE-2026-14052: Insufficient policy enforcement in FileSystem.
• [501836539] Low CVE-2026-14053: Insufficient policy enforcement in Extensions.
• [501851312] Low CVE-2026-14054: Insufficient policy enforcement in Network.
• [501857663] Low CVE-2026-14055: Insufficient validation of untrusted input in Device Trust.
• [501888426] Low CVE-2026-14056: Insufficient validation of untrusted input in Media.
• [502212647] Low CVE-2026-14057: Insufficient policy enforcement in FedCM.
• [502354038] Low CVE-2026-14058: Policy bypass in Parser.
• [502363986] Low CVE-2026-14059: Insufficient policy enforcement in Related-Website-Sets.
• [502372527] Low CVE-2026-14060: Insufficient validation of untrusted input in Chromoting.
• [502434484] Low CVE-2026-14061: Inappropriate implementation in Dawn.
• [502448128] Low CVE-2026-14062: Inappropriate implementation in Views.
• [502473563] Low CVE-2026-14063: Out of bounds memory access in Chromecast.
• [502714977] Low CVE-2026-14064: Use after free in PageInfo.
• [503617508] Low CVE-2026-14065: Insufficient validation of untrusted input in PageInfo.
• [503779807] Low CVE-2026-14066: Insufficient validation of untrusted input in Chrome for iOS.
• [504069465] Low CVE-2026-14067: Use after free in Chrome for iOS.
• [504210171] Low CVE-2026-14068: Inappropriate implementation in Omnibox.
• [505136542] Low CVE-2026-14069: Integer overflow in WebNN.
• [505137978] Low CVE-2026-14070: Uninitialized Use in WebNN.
• [506143724] Low CVE-2026-14071: Side-channel information leakage in WebAudio.
• [507099867] Low CVE-2026-14072: Incorrect security UI in SplitView.
• [507237563] Low CVE-2026-14073: Insufficient policy enforcement in WebXR.
• [511743480] Low CVE-2026-14074: Side-channel information leakage in WebAuthentication.
• [511808800] Low CVE-2026-14075: Policy bypass in Chrome for iOS.
• [511815165] Low CVE-2026-14076: Policy bypass in Network.
• [511869411] Low CVE-2026-14077: Incorrect security UI in Select.
• [512953564] Low CVE-2026-14078: Policy bypass in WebRTC.
• [512971938] Low CVE-2026-14079: Policy bypass in Network.
• [512997517] Low CVE-2026-14080: Insufficient validation of untrusted input in TabSwitcher.
• [513030698] Low CVE-2026-14081: Insufficient policy enforcement in DevTools.
• [513049578] Low CVE-2026-14082: Race in Storage.
• [513128322] Low CVE-2026-14083: Insufficient validation of untrusted input in HTML.
• [513138148] Low CVE-2026-14084: Insufficient validation of untrusted input in Chromoting.
• [513155863] Low CVE-2026-14085: Side-channel information leakage in CSS.
• [513169718] Low CVE-2026-14086: Insufficient policy enforcement in HID.
• [513177237] Low CVE-2026-14087: Insufficient validation of untrusted input in WebNN.
• [513178869] Low CVE-2026-14088: Uninitialized Use in Canvas.
• [513188254] Low CVE-2026-14089: Insufficient validation of untrusted input in PopupBlocker.
• [513194241] Low CVE-2026-14090: Out of bounds read in CameraCapture.
• [513208773] Low CVE-2026-14091: Use after free in DevTools.
• [513212892] Low CVE-2026-14092: Insufficient policy enforcement in Privacy.
• [513240099] Low CVE-2026-14093: Use after free in Cast.
• [513264273] Low CVE-2026-14094: Use after free in Installer.
• [513271007] Low CVE-2026-14095: Insufficient validation of untrusted input in Browser.
• [513310821] Low CVE-2026-14096: Object lifecycle issue in Input.
• [513333529] Low CVE-2026-14097: Inappropriate implementation in WebAppInstalls.
• [513375767] Low CVE-2026-14098: Inappropriate implementation in CSS.
• [513382161] Low CVE-2026-14099: Use after free in Chrome for iOS.
• [513383891] Low CVE-2026-14100: Insufficient data validation in NetworkCache.
• [513454805] Low CVE-2026-14101: Insufficient policy enforcement in Sandbox.
• [513455047] Low CVE-2026-14102: Use after free in Passwords.
• [513465245] Low CVE-2026-14103: Use after free in SSL.
• [513484193] Low CVE-2026-14104: Insufficient validation of untrusted input in WebAppInstalls.
• [513528117] Low CVE-2026-14105: Insufficient policy enforcement in Speech.
• [513532778] Low CVE-2026-14106: Insufficient validation of untrusted input in Text.
• [513544566] Low CVE-2026-14107: Use after free in Scheduling.
• [513689974] Low CVE-2026-14108: Use after free in PDFium.
• [513694957] Low CVE-2026-14109: Insufficient policy enforcement in Mojo.
• [513698452] Low CVE-2026-14110: Inappropriate implementation in DarkMode.
• [513710926] Low CVE-2026-14111: Use after free in WebProtect.
• [513713946] Low CVE-2026-14112: Inappropriate implementation in Enterprise.
• [513737335] Low CVE-2026-14113: Use after free in Updater.
• [513743129] Low CVE-2026-14114: Inappropriate implementation in WebAppInstalls.
• [513745699] Low CVE-2026-14115: Insufficient validation of untrusted input in Cast.
• [513747800] Low CVE-2026-14116: Insufficient validation of untrusted input in DevTools.
• [513751020] Low CVE-2026-14117: Insufficient validation of untrusted input in DevTools.
• [513772764] Low CVE-2026-14118: Insufficient data validation in DevTools.
• [513775483] Low CVE-2026-14119: Type Confusion in Bluetooth.
• [513777411] Low CVE-2026-14120: Inappropriate implementation in DevTools.
• [513789382] Low CVE-2026-14121: Use after free in Chromoting.
• [513824891] Low CVE-2026-14122: Insufficient validation of untrusted input in WebAppInstalls.
• [513856644] Low CVE-2026-14123: Incorrect security UI in Chrome for iOS.
• [513867710] Low CVE-2026-14124: Inappropriate implementation in CredentialProvider.
• [513918431] Low CVE-2026-14125: Uninitialized Use in ANGLE.
• [513992796] Low CVE-2026-14126: Incorrect security UI in UI.
• [514009654] Low CVE-2026-14127: Inappropriate implementation in Printing.
• [514015836] Low CVE-2026-14128: Insufficient data validation in Chrome for iOS.
• [514018024] Low CVE-2026-14129: Incorrect security UI in PreviewTab.
• [514019522] Low CVE-2026-14130: Incorrect security UI in Omnibox.
• [514020982] Low CVE-2026-14131: Insufficient validation of untrusted input in WebAppInstalls.
• [514039492] Low CVE-2026-14132: Inappropriate implementation in WebXR.
• [514039947] Low CVE-2026-14133: Race in History Embeddings.
• [514055973] Low CVE-2026-14134: Inappropriate implementation in Autofill.
• [514058566] Low CVE-2026-14135: Insufficient validation of untrusted input in Network.
• [514068611] Low CVE-2026-14136: Incorrect security UI in Chrome for iOS.
• [514070067] Low CVE-2026-14137: Insufficient validation of untrusted input in Chrome for iOS.
• [514071775] Low CVE-2026-14138: Inappropriate implementation in WebAppInstalls.
• [514072495] Low CVE-2026-14139: Inappropriate implementation in TabStrip.
• [514072607] Low CVE-2026-14140: Insufficient validation of untrusted input in Input.
• [514072867] Low CVE-2026-14141: Incorrect security UI in Document Picture-in-Picture.
• [514073460] Low CVE-2026-14142: Inappropriate implementation in Extensions.
• [514075028] Low CVE-2026-14143: Incorrect security UI in Passwords.
• [514079793] Low CVE-2026-14144: Incorrect security UI in Views.
• [514485825] Low CVE-2026-14145: Inappropriate implementation in CSS.
• [514550047] Low CVE-2026-14146: Inappropriate implementation in CSS.
• [514632767] Low CVE-2026-14147: Inappropriate implementation in CSS.
• [515426873] Low CVE-2026-14148: Type Confusion in CSS.
• [515427046] Low CVE-2026-14149: Use after free in Audio.
• [517376041] Low CVE-2026-14150: Insufficient validation of untrusted input in Speech.
• [517381770] Low CVE-2026-14151: Inappropriate implementation in AI.
• [517534944] Low CVE-2026-14152: Out of bounds write in ANGLE.
• [517684077] Low CVE-2026-14153: Inappropriate implementation in Glic.
• [517741170] Low CVE-2026-14154: Inappropriate implementation in DevTools.
• [518246925] Low CVE-2026-14155: Insufficient policy enforcement in StorageAccessAPI.
• [518247789] Low CVE-2026-14156: Policy bypass in StorageAccessAPI.

The OpenVPN community project team reports:

[...] OpenVPN 2.7.5 [...] is a bugfix release fixing several security issues:

• Fix use-after-free bug in ack_write_buf(), triggerable by a well-timed sequence of control channel + authentication packets (CVE-2026-12996)
• Fix use-after-free bug in tls_wrap_reneg(), triggerable by suitable sequence of dynamic tls-crypt control-channel packets (CVE-2026-13117)
• Fix server crash on reception of suitably malformed auth-token, if --auth-gen-token external-auth is active (CVE-2026-13122)
• Fix memory-leak in tls-crypt-v2 client key handling that could lead to out-of-memory situations and subsequent server crashes (CVE-2026-12932)
• Fix possible 1-byte buffer overrun on NTLMv2 proxy responses. (CVE-2026-11771)
• Fix another memory leak on reception of suitable tls-crypt-v2 packets that could lead to an out of memory situation and server crash (CVE-2026-13698)

Problem Description:

Several encoding modules, including HZ, UTF-7, VIQR, and ZW, did not properly check the size of the caller-supplied output buffer before writing converted characters. [CVE-2026-58081]

The ISO-2022 encoding module used a stack buffer sized to MB_LEN_MAX (6 bytes) for intermediate character output. Some ISO-2022 variants can require up to 10 bytes per character, in which case conversions can trigger a stack buffer overflow of up to four bytes. [CVE-2026-58082]

Impact:

An application that uses iconv(3) to convert untrusted input to or from one of the affected encodings may be vulnerable to buffer overflows if it uses one of the affected encoding modules.

Problem Description:

The compat32 kevent() handler translates a 64-bit kevent struct into a stack- declared 32-bit struct. It did not first zero the stack struct.

Impact:

An unprivileged user may observe a small amount of uninitialized kernel stack data, which may contain sensitive information.

Problem Description:

The Linux waitid() implementation translates a FreeBSD siginfo_t struct into a stack-declared Linux siginfo_t. It did not first zero the stack struct.

Impact:

An unprivileged user may observe 104 bytes of uninitialized kernel stack data, which may contain sensitive information.

Problem Description:

When building the iovec array for a received TLS 1.2 CBC record, ktls_ocf_tls_cbc_decrypt() incremented the iovec index for every mbuf in the chain, including mbufs that were skipped because they contained only TLS header bytes. This left uninitialized entries in the iovec array. The iovec array was allocated without zeroing.

Impact:

A remote TLS peer can cause the kernel to read from uninitialized iovec entries during HMAC computation, resulting in a kernel panic. The peer must be able to control TCP segmentation such that the first mbuf of a CBC record contains only the 5-byte TLS record header.

Problem Description:

When auditing a system call executed via ptrace(PT_SC_REMOTE), the kernel passed the return value of an internal setup function to AUDIT_SYSCALL_EXIT() rather than the actual result of the executed system call. As a result, committed audit records for system calls which returned an error do not reflect the true outcome of the operation. That is, they indicate that the operation succeeded when it in fact failed.

Impact:

Audit records for system calls executed via ptrace(PT_SC_REMOTE) may show an incorrect error status. An attacker with the ability to debug a process could use this to produce misleading audit trails, potentially undermining audit-based Intrusion Detection Systems (IDS).

Problem Description:

Pages belonging to largepage shared memory objects were not explicitly wired. When sendfile(2) transmitted such an object with the SF_NOCACHE flag, it freed the underlying pages after transmission even though existing mappings still referred to them. [CVE-2026-49427]

Separately, certain system calls, such open(2) with the O_TRUNC flag set, and fspacectl(2), could incorrectly free memory in largepage objects. These operations are not permitted on largepage objects, but the implementation did not verify this. [CVE-2026-49428]

Impact:

An unprivileged local user can abuse the bug to access freed kernel memory. This can be exploited to escalate privileges.

Problem Description:

The RACK setsockopt(2) handler drops the connection lock in order to copy option data from userspace, then reacquires the lock. After reacquiring, it verifies that the TCP stack had not been switched away, but did not reload its pointer to the stack's per-connection control block. If userspace switches stacks twice during this window, the check will succeed but the saved pointer will refer to freed memory.

Impact:

The bug may be exploitable by an unprivileged local user to escalate privileges.

Problem Description:

The kernel function that implements unlinkat(2) and funlinkat(2) validated the AT_RESOLVE_BENEATH flag but failed to pass it through to the underlying path lookup. The flag was silently dropped, so path resolution was not actually restricted.

Impact:

A process that uses AT_RESOLVE_BENEATH with unlinkat(2) or funlinkat(2) to confine path resolution can in fact resolve paths above the starting directory. A caller relying on this flag for path containment may delete files outside the intended directory tree.

Problem Description:

The RTSP handler in libalias rewrote outgoing packets into a fixed-length stack buffer without checking whether the rewritten data fit in the buffer, or whether the result fit back in the original packet.

Impact:

A host sending crafted RTSP traffic from inside a NAT gateway using libalias can overflow a stack buffer, potentially achieving remote code execution in the kernel (when using ipfw(4) NAT) or in the natd(8) process (which generally runs as the root user).

Problem Description:

The ZFS_IOC_USERSPACE_MANY ioctl, used by zfs-userspace(8), truncated a 64-bit output buffer size to a 32-bit integer for the kernel allocation, but used the original 64-bit size as the buffer limit when writing records.

The ZFS_IOC_RECV_NEW ioctl, in the heal receive path, similarly truncated a 64-bit payload size to a 32-bit integer for allocation, then used the original 64-bit size as the length for a byteswap operation.

The ZFS_IOC_SET_PROP ioctl, used by zfs-set(8), incorrectly validated the calling user such that an unprivileged user is able to set metadata on a dataset indicating that the dataset has received properties from a zfs-recv(8) stream.

Impact:

A local user with the "userused" delegated ZFS permission can trigger a kernel heap overflow via the ZFS_IOC_USERSPACE_MANY ioctl, potentially escalating privileges. [CVE-2026-49429]

A local user with the "receive" delegated ZFS permission can trigger kernel memory corruption via ZFS_IOC_RECV_NEW by sending a crafted receive stream in heal mode. [CVE-2026-49430]

Any local user can set the internal ZFS metadata flag "$hasrecvd" on datasets via ZFS_IOC_SET_PROP. [CVE-2026-49431]

Problem Description:

During execve(2) of a SUID binary, the new virtual address space is installed before the process credentials are updated. During this window, a process running as the same user can access the target process's memory via procfs or linprocfs, because the kernel's debugging permission check still saw the original credentials.

Impact:

An unprivileged local user can exploit this race to modify the address space of a SUID binary before its credentials are elevated, potentially gaining full control of the affected system.

Problem Description:

When the JAIL_AT_DESC flag is specified, kern_jail_set() and kern_jail_get() released the reference to the caller's current prison before looking up the jail descriptor. If the descriptor lookup failed, error-handling paths released the same reference a second time.

Impact:

An unprivileged local user can trigger a prison reference count underflow, which may cause the prison structure to be freed while still in use. When this is done on the jail host, the bug will generally result in an immediate panic. However, if the user is running in a jail, then it may be possible to exploit the bug to elevate privileges.

Problem Description:

When msync(MS_INVALIDATE) is called on a mapping of an unmanaged device object, the physical pages in the mapping range are marked invalid but remain in the pager's page list. A subsequent page fault will cause the fault handler to re-insert the page into the object's list. This corrupts the list, and on object destruction the page is freed twice.

Impact:

An unprivileged local user with access to a device that provides memory-mapped I/O can trigger a use-after-free in the kernel, though this is limited to a pool of objects ("fictitious pages") that are never recycled for a different purpose. It may be possible to exploit this to escalate privileges.

The Icinga team reports:

The code handling certificate update JSON-RPC messages was flawed and did not properly validate the sender of the message, allowing an unauthenticated attacker that can connect to Icinga 2 to update both the own certificate as well as the trusted CA certificate. Updating the trusted CA allows an attacker to impersonate a trusted node, allowing them to take control over the node.

Any Icinga 2 instance that is accessible to an attacker over the network is affected.

PostgreSQL project reports:

channelBinding=require connections can be silently downgraded from SCRAM-SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it), losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection triggers the downgrade with a certificate whose signature algorithm has no tls-server-end-point channel-binding hash. Examples are Ed25519, Ed448, and post-quantum algorithms.

Chrome Releases reports:

This update includes 3 security fixes:

• [513138301] High CVE-2026-13281: Integer overflow in Mojo. Reported by Google on 2026-05-14
• [517522620] High CVE-2026-13282: Use after free in Payments. Reported by Google on 2026-05-28
• [522561151] High CVE-2026-13283: Use after free in AdFilter. Reported by Google on 2026-06-11

NLnet Labs reports:

CVE-2026-12244: A specially crafted SVCB RR can cause a heap overflow of up to 65509 attacker controlled bytes.

If NSD is configured as secondary for a zone, the primary of that zone can crash NSD with an AXFR containing a DNS message with a special crafted SVCB RR with an rdata size of 65512, that let's an (uint16_t) variable that is used to allocate space needed for the RR wrap (because total size > 65535), causing a heap overflow. The attacker can perform a controlled (RCE class) head write of up to 65509 bytes

Even though the data is from a configured primary inside NSD's trust boundary, we do consider the risk significant enough for multi-tenant secondary DNS deployments, given the potential severity of the attack.

CVE-2026-12245: An attacker can keep all children in a crash-restart loop denying DoT service.

NSD from version 4.13.0 has a heap use-after-free bug in logging errors on TLS connections, causing a crash of the server process, which can be triggered trivially by sending a DNS query over a DoT connection, and closing the connection without reading the response.

Any client with access to the DoT port (853) can trigger this. Even though a new server process will be immediately reforked to replace the crashed one, an attacker can keep all children in a crash-restart loop denying DoT service.

CVE-2026-12246: The RR type APL rdata address, if too large, causes out of bounds write on the stack, when the zonefile is written out.

NSD version 4.14.0 introduced a bug where a specially crafted APL RR, with an adflength larger than permitted for the address family will overwrite the stack when the zone is written to disk, with a maximum of 111 attacker controlled bytes.

Even though the data is from a configured primary inside NSD's trust boundary, we do consider the risk significant enough for multi-tenant secondary DNS deployments, where a primary could introduce the rogue APL with the secondary not noticing or only after the fact.

CVE-2026-12490: Secondaries authenticated by a client certificate to transfer a zone over TLS, can bypass verification by transferring over TCP.

When a "provide-xfr" is given with a "tls-auth-name", a secondary requesting a transfer should provide a client certificate with that name. However, no client certificate is needed when the request comes in over TLS over the regular "tls-port" (and not the "tls-auth-port") or over over TCP over the regular port, when the other conditions of the "provide-xfr" rule match.

The transfer security restrictions for client certificates can be bypassed completely if the attacker can match the other access control conditions, and the "tls-auth-xfr-only" option is not explicitly set to "yes" (which it by default is not)

Thanks to people below for reporting and disclosing these vulnerabilities:

• Qifan Zhang from Palo Alto Networks
• Haruki Oyama from Waseda University
• zhangph

https://github.com/rclone/rclone/security/advisories/GHSA-qw24-gh76-8rvv reports:

Rclone is a command-line program to sync files and directories to and from different cloud storage providers.
From 1.46.0 until 1.74.3, rclone rcd --rc-serve accepts unauthenticated GET and HEAD requests to paths of the form: /[remote:path]/object.
The remote value is parsed from the URL and passed to normal backend initialization. Inline remote configuration can set backend options that execute local commands during initialization.
As a result, a single unauthenticated GET or HEAD request can execute a command as the rclone process user.

Thanks to Nick Craig-Wood for reporting this vulnerability.

PowerDNS Team reports:

• CVE-2026-33257: Insufficient input validation of internal webserver
• CVE-2026-33260: Insufficient input validation of internal webserver
• CVE-2026-33608: Incomplete domain name sanitization during Bind autosecondary zone transfer
• CVE-2026-33609: LDAP DN injection
• CVE-2026-33610: Possible file descriptor exhaustion in forward-dnsupdate
• CVE-2026-33611: Insufficient validation of HTTPS and SVCB records

Thanks to people below for reporting these vulnerabilities:

• Vitaly Simonovich
• Cavid
• Tibs
• ylwango613

• CVE-2026-42005: Insufficient input validation of internal web server

Thanks to ilya rozentsvaig for reporting this vulnerability.

PowerDNS Team reports:

• CVE-2026-3361: ZoneToCache can poison the cache
• CVE-2026-40012: Information about ECS zero scoped answers might leak to clients that use a specific ECS
• CVE-2026-42005: Unbounded resource consumption in internal webserver
• CVE-2026-42387: Insufficient input validation in ZoneToCache
• CVE-2026-42388: Missing input validation for catalog zones
• CVE-2026-42389: Reject more queries with invalid header values
• CVE-2026-42390: ZONEMD validation can be bypassed
• CVE-2026-52690: Spoofed answers can mark an authoritative non-EDNS capable

Thanks to people below for reporting these vulnerabilities.

• Danial Mahadzir
• ilya rozentsvaig
• Vitaly Simonovich
• ylwango613
• nurmukhammyed
• Mehtab Zafar

The DNSdist team reports:

• CVE-2026-40011: Prometheus denial of service via crafted DNS queries
• CVE-2026-42004: EDNS options smuggling
• CVE-2026-42005: Insufficient input validation of internal web server
• CVE-2026-40208: Denial of service via DoH3 queries
• CVE-2026-40209: Denial of service via IXFR queries
• CVE-2026-40210: Out-of-bounds read in SetMacAddrAction
• CVE-2026-40211: Denial of service via crafted DoH3 queries

Thanks to people below for reporting these vulnerabilities.

• Haruki Oyama (Waseda University)
• Vitaly Simonovich
• ilya rozentsvaig
• ylwango613
• Qifan Zhang (Palo Alto Networks)
• Mehtab Zafar

The GStreamer project reports:

Multiple security issues were identified and fixed in the GStreamer framework.

• GStreamer-SA-2026-0030: Missing bounds checks in RTCP SDES packet parsing
• GStreamer-SA-2026-0031: Integer overflow and truncation in MXF demuxer
• GStreamer-SA-2026-0032: Out-of-bounds read and write in XMP tag parser
• GStreamer-SA-2026-0033: Out-of-bounds read and modification of const data in ID3v2 parser
• GStreamer-SA-2026-0034: Division by zero in mDVDsub subtitle parser
• GStreamer-SA-2026-0035: Integer overflow in WavPack decoder
• GStreamer-SA-2026-0036: Out-of-bounds read in SBC audio parser header parsing
• GStreamer-SA-2026-0037: Heap corruption in gst-libav AV protocol pipe
• GStreamer-SA-2026-0038: Memory leak and NULL pointer dereference in gst-libav demuxer
• GStreamer-SA-2026-0039: Assertion in AV1 parser tile data parsing
• GStreamer-SA-2026-0040: Out-of-bounds read in VA JPEG decoder segment parsing
• GStreamer-SA-2026-0042: Out-of-bounds reads and integer overflows in RealMedia demuxer
• GStreamer-SA-2026-0043: Out-of-bounds read and write in RFB source
• GStreamer-SA-2026-0045: Out-of-bounds reads in PCAP parser due to missing bounds checks
• GStreamer-SA-2026-0046: Integer overflow in VMNC decoder cursor payload size calculation
• GStreamer-SA-2026-0047: One-byte out-of-bounds read in H.264 NAL unit parser
• GStreamer-SA-2026-0048: Out-of-bounds read in H.266 parser VUI aspect ratio parsing

Expat 2.8.2 was released yesterday. The key motivation for cutting a release and doing so now was

getting security and non-security bugsfixes out to users. On the security side,

13 vulnerabilities have been fixed:

• CVE-2026-50219: missing control flow integrity checks
• CVE-2026-56131: missing control flow integrity checks
• CVE-2026-56132: out-of-bounds write
• CVE-2026-56403: integer overflow
• CVE-2026-56404: integer overflow
• CVE-2026-56405: integer overflow
• CVE-2026-56406: integer overflow
• CVE-2026-56407: integer overflow
• CVE-2026-56408: integer overflow
• CVE-2026-56409: integer overflow
• CVE-2026-56410: integer overflow
• CVE-2026-56411: integer overflow
• CVE-2026-56412: missing control flow integrity checks

The Gitea team reports:

• CVE-2026-27783: incorrect read permission check
• CVE-2026-25714: public-only token filtering bypass
• CVE-2026-20706: missing token scope checking
• CVE-2026-27771: unauthenticated access to private container images
• CVE-2026-28744: git smart HTTP request scope bug
• CVE-2026-28699: basic auth bug
• CVE-2026-26231: maintainer edit permission escalation
• CVE-2026-20896: reverse proxy trusted proxies misconfiguration allowing user impersonation
• CVE-2026-22874: incomplete SSRF protection in webhooks and migrations
• CVE-2026-27775: branch write permission cache escalation
• CVE-2026-27761: RSS/Atom feed token scope not enforced
• CVE-2026-25038: private organization labels leaked to non-members
• CVE-2026-24451: fork sync allowed after base repo access revoked
• CVE-2026-20779: TOTP passcode reuse across login surfaces (TOCTOU race)
• CVE-2026-28740: cross-repository LFS object reuse without Code-unit access
• OAuth2 callback could auto-reactivate disabled users

https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/23159 reports:

An out-of-bounds write vulnerability in FFmpeg's libavcodec library, specifically in the MagicYUV decoder, allows denial-of-service and, in some cases, can be exploited for remote code execution. This vulnerability is associated with the file libavcodec/magicyuv.C. This issue affects FFmpeg before version 8.1.2.

Gitlab reports:

Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE

Cross-site Scripting issue in Web IDE workbench asset handler impacts GitLab CE/EE

Information Disclosure issue in Duo Workflows impacts GitLab EE

Authorization Bypass issue in Virtual Registry Cleanup Policy API impacts GitLab EE

Improper Authorization issue in Rapid Diffs impacts GitLab CE/EE

Incorrect Authorization issue in DAST scanner and site profile management impacts GitLab EE

Insufficient Filtering issue in CI/CD API impacts GitLab CE/EE

Improper Input Validation issue in Snippets impacts GitLab CE/EE

Incorrect Authorization issue in Maven Package Registry impacts GitLab CE/EE

Improper Access Control issue in group packages API impacts GitLab CE/EE

Improper Access Control issue in Protected Environments API impacts GitLab EE

Missing Authorization issue in Security Dashboard impacts GitLab EE

Server-Side Request Forgery issue in Repository Mirroring impacts GitLab CE/EE

The go-git project reports:

See link for details.

https://www.nlnetlabs.nl/downloads/ldns/CVE-2026-10846.txt reports:

NLnet Labs ldns 1.2.0 up to and including versions 1.9.0, when used in applications as (stub) resolver over UDP, lacks matching the query destination address and port with the response source address and port. Furthermore not the query ID, neither the question of the query is matched with that of the response. This makes applications, that use ldns for (stub) resolver functionality over UDP, vulnerable for off-path poisoning attacks. The drill tool, which is shipped with ldns, suffers from this vulnerability.

We would like to thank Pablo Ruiz from codecome.ai for finding and reporting this vulnerability.

The Podman developers report:

Building a Dockerfile using an ADD or COPY instruction accessing a malicious Git repository or tar archive could cause files outside the build context directory to be included in the build context or copied into the build.

The nginx developers report:

A heap memory buffer overflow vulnerability when using the "ignore_invalid_headers off;" and "large_client_header_buffers" directives with large configured values while proxying a specially crafted request to an HTTP/2 or gRPC backend may allow memory corruption or a segmentation fault in a worker process (CVE-2026-42055).

A heap memory buffer overread vulnerability while handling a specially crafted response with decoding from UTF-8 via the "charset_map" directive may allow limited disclosure of worker process memory or a segmentation fault in a worker process (CVE-2026-48142).

The nginx developers report:

A use-after-free vulnerability when using HTTP/3 and processing a specially crafted QUIC session may allow memory corruption or a segmentation fault in a worker process (CVE-2026-42530).

A heap memory buffer overflow vulnerability when using the "ignore_invalid_headers off;" and "large_client_header_buffers" directives with large configured values while proxying a specially crafted request to an HTTP/2 or gRPC backend may allow memory corruption or a segmentation fault in a worker process (CVE-2026-42055).

A heap memory buffer overread vulnerability while handling a specially crafted response with decoding from UTF-8 via the "charset_map" directive may allow limited disclosure of worker process memory or a segmentation fault in a worker process (CVE-2026-48142).

Jenkins Security Advisory 2026-06-10:

• SECURITY-3707 / CVE-2026-53435: Deserialization vulnerability (High)
• SECURITY-3711+3755 / CVE-2026-53436, CVE-2026-53437: Open redirect vulnerability (Medium)
• SECURITY-3712 / CVE-2026-53438: Missing permission check allows canceling queue items (Medium)
• SECURITY-3713 / CVE-2026-53439: Missing permission checks allow obtaining limited user profile information (Medium)
• SECURITY-3721 / CVE-2026-53440: Open redirect vulnerability in "Delegate to servlet container" security realm (Medium)
• SECURITY-3731 / CVE-2026-53441: Stored XSS vulnerability in node offline cause description (High)
• SECURITY-3744 / CVE-2026-53442: Plaintext secrets persisted and served by config.xml endpoints (Medium)

https://www.nlnetlabs.nl/downloads/routinator/CVE-2026-49235.txt reports:

When Routinator encounters a file via RRDP using a specifically crafted Document Type Definition, Routinator crashes.

Thanks to X41 D-Sec GmbH for reporting the vulnerability.

https://www.nlnetlabs.nl/downloads/routinator/CVE-2026-49234.txt reports:

When sending a specifically crafted non-UTF-8 string as select-asn query parameter to the /api/v1/origins endpoint, Routinator crashes. This only affects users who allow API access from untrusted networks.

Thanks to X41 D-Sec GmbH for reporting the vulnerability.

https://www.nlnetlabs.nl/downloads/routinator/CVE-2026-49233.txt reports:

Routinator does not properly check the module component of rsync URIs, which are used to create the file system paths for the Routinator cache. This allows for path traversal by having a module name containing .., potentially providing an attacker access to the entire Routinator rsync cache.

Thanks to X41 D-Sec GmbH for reporting the vulnerability.

https://www.nlnetlabs.nl/downloads/routinator/CVE-2026-49232.txt reports:

Routinator exits on any error when accepting incoming HTTP or RTR connections, including ones it can recover from such as running out of file descriptors. This condition can be triggered maliciously by an attacker by opening a large number of connections to the HTTP or RTR server. This only affects users that make their HTTP or RTR server available to untrusted networks.

Thanks to X41 D-Sec GmbH for reporting the vulnerability.

Chrome Releases reports:

This update includes 33 security fixes:

• [516496659] Critical CVE-2026-12437: Use after free in WebShare.
• [516947912] Critical CVE-2026-12438: Inappropriate implementation in WebView.
• [519728275] Critical CVE-2026-12439: Use after free in Digital Credentials.
• [519731619] Critical CVE-2026-12440: Use after free in DigitalCredentials.
• [520157118] Critical CVE-2026-12441: Use after free in File Input.
• [521950423] Critical CVE-2026-12442: Use after free in Passwords.
• [522566295] Critical CVE-2026-12443: Use after free in Web Authentication.
• [513160088] High CVE-2026-12444: Out of bounds read in Chromoting.
• [513199795] High CVE-2026-12445: Use after free in Extensions.
• [513313107] High CVE-2026-12446: Insufficient data validation in Passwords.
• [513405023] High CVE-2026-12447: Heap buffer overflow in WebRTC.
• [513458233] High CVE-2026-12448: Inappropriate implementation in WebView.
• [513480539] High CVE-2026-12449: Use after free in Chromoting.
• [514531776] High CVE-2026-12450: Inappropriate implementation in Media.
• [514741076] High CVE-2026-12451: Use after free in DigitalCredentials.
• [515462244] High CVE-2026-12452: Use after free in Downloads.
• [516448843] High CVE-2026-12453: Insufficient validation of untrusted input in Input.
• [516926968] High CVE-2026-12454: Race in Safe Browsing.
• [517069848] High CVE-2026-12455: Use after free in Tab Strip.
• [517124587] High CVE-2026-12456: Insufficient validation of untrusted input in Extensions.
• [517153117] High CVE-2026-12457: Insufficient data validation in Extensions.
• [517258337] High CVE-2026-12458: Incorrect security UI in Passwords.
• [517406035] High CVE-2026-12459: Inappropriate implementation in Serial.
• [517484284] High CVE-2026-12460: Insufficient policy enforcement in File System Access.
• [517727318] High CVE-2026-12461: Out of bounds read in WebRTC.
• [517916024] High CVE-2026-12462: Use after free in Media.
• [518042749] High CVE-2026-12463: Inappropriate implementation in Views.
• [519358344] High CVE-2026-12464: Use after free in Browser.
• [520189702] High CVE-2026-12465: Insufficient validation of untrusted input in Metrics.
• [520199394] High CVE-2026-12466: Heap buffer overflow in WebRTC.
• [520202726] High CVE-2026-12467: Use after free in Extensions.
• [521485244] High CVE-2026-12468: Inappropriate implementation in Updater.
• [521618871] High CVE-2026-12469: Uninitialized Use in GPU.

Mailpit authorreports:

The tools.IsInternalIP deny-list relies on Go's stdlib classification helpers (IsLoopback, IsPrivate, IsLinkLocalUnicast, IsLinkLocalMulticast, IsUnspecified, IsMulticast) plus an inline CGNAT range, but those helpers do not match two classes of IPv6 address that should be blocked for SSRF purposes

Chrome Releases reports:

This update includes 28 security fixes:

• [516731749] Critical CVE-2026-12007: Use after free Core. Reported by Google on 2026-05-26
• [516942828] Critical CVE-2026-12008: Use after free DigitalCredentials. Reported by Google on 2026-05-27
• [517332006] Critical CVE-2026-12009: Insufficient validation of untrusted input ccessibility. Reported by Google on 2026-05-28
• [517531647] Critical CVE-2026-12010: Heap buffer overflow GPU. Reported by Google on 2026-05-28
• [518108291] Critical CVE-2026-12011: Use after free WebMIDI. Reported by Google on 2026-05-30
• [499182801] High CVE-2026-12012: Use after free etwork. Reported by Google on 2026-04-03
• [514229805] High CVE-2026-12013: Use after free Media. Reported by Henock Habte, Independent Security Researcher on 2026-05-18
• [514742747] High CVE-2026-12014: Use after free Cast. Reported by Google on 2026-05-19
• [515463295] High CVE-2026-12015: Use after free utofill. Reported by Google on 2026-05-21
• [516482138] High CVE-2026-12016: Insufficient validation of untrusted input DevTools. Reported by Google on 2026-05-25
• [516797143] High CVE-2026-12017: Insufficient validation of untrusted input Extensions. Reported by Google on 2026-05-26
• [516808201] High CVE-2026-12018: Inappropriate implementation Mojo. Reported by Google on 2026-05-26
• [516872067] High CVE-2026-12019: Out of bounds write Codecs. Reported by Google on 2026-05-26
• [516907083] High CVE-2026-12020: Use after free utofill. Reported by Google on 2026-05-27
• [516929496] High CVE-2026-12022: Race Safe Browsing. Reported by Google on 2026-05-27
• [517018374] High CVE-2026-12023: Use after free GPU. Reported by Google on 2026-05-27
• [517086161] High CVE-2026-12024: Insufficient policy enforcement DevTools. Reported by Google on 2026-05-27
• [517153191] High CVE-2026-12025: Insufficient validation of untrusted input etwork. Reported by Google on 2026-05-27
• [517347084] High CVE-2026-12026: Out of bounds read Video. Reported by Google on 2026-05-28
• [517517155] High CVE-2026-12027: Insufficient policy enforcement Headless. Reported by Google on 2026-05-28
• [517555461] High CVE-2026-12028: Use after free GPU. Reported by Google on 2026-05-28
• [518002958] High CVE-2026-12029: Use after free Video. Reported by Google on 2026-05-29
• [518007423] High CVE-2026-12030: Heap buffer overflow GPU. Reported by Google on 2026-05-29
• [518045638] High CVE-2026-12031: Inappropriate implementation Views. Reported by Google on 2026-05-30
• [518128953] High CVE-2026-12032: Inappropriate implementation Passwords. Reported by Google on 2026-05-30
• [519248779] High CVE-2026-12033: Out of bounds read VideoCapture. Reported by Google on 2026-06-02
• [519258799] High CVE-2026-12034: Insufficient validation of untrusted input Linux Toolkit Theming. Reported by Google on 2026-06-02
• [520210566] High CVE-2026-12035: Use after free Views. Reported by Google on 2026-06-05

http://lists.opensuse.org/opensuse-security-announce/2011-01/msg00003.html reports:

Buffer overflow in the smiGetNode function in lib/smi.c in libsmi 0.4.8 allows context-dependent attackers to execute arbitrary code via an Object Identifier (aka OID) represented as a numerical string containing many components separated by . (dot) characters.

The traefik project releases a new version addressing multiple CVEs:

• CVE-2026-48020 (StripPrefix Route-Level Auth Bypass)
• CVE-2026-48491 (SNICheck ignores wildcard TLSOptions mappings, allowing domain-fronted mTLS bypass)
• HTTP/3 mTLS bypass via exact SNI TLSOptions lookup for wildcard and mixed-case hosts

Caddy project reports:

Caddy 2.11.4 contains multiple security fixes.

GitHub Security Advisory GHSA-qrp7-cvwr-j2c6 reports:

Windows-encoded backslashes in request paths could bypass path-scoped authorization rules before files are served by file_server.

GitHub Security Advisory GHSA-f59h-q822-g45g reports:

forward_auth copy_headers could fail to remove underscore aliases of copied identity headers before FastCGI header normalization, allowing identity or group header spoofing.

GitHub Security Advisory GHSA-vcc4-2c75-vc9v reports:

The stripHTML template function could fail to remove malformed HTML, potentially allowing client-side cross-site scripting if untrusted output is later rendered as HTML.

Gitlab reports:

Improper Access Control issue in Group SAML Identity API impacts GitLab EE

Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE

Denial of Service issue in Grape API JSON parsing middleware impacts GitLab CE/EE

HTML injection issue in certain group setting fields impacts GitLab EE

Denial of Service issue in Group Placeholder Reassignments API impacts GitLab CE/EE

Improper Access Control issue in Merge Requests API impacts GitLab CE/EE

Server-Side Request Forgery issue in Gitaly repository import impacts GitLab CE/EE

HTML injection issue in CI/CD Catalog impacts GitLab CE/EE

Improper Access Control issue in Security Inventory impacts GitLab EE

Authorization Bypass issue in Merge Request diff impacts GitLab CE/EE

Improper Access Control issue in Todos API impacts GitLab CE/EE

Improper Neutralization issue in Service Desk email template impacts GitLab CE/EE

h2o project reports:

When serving static files, h2o can allocate a file path on the stack using alloca. On systems using musl libc, a large allocation can exceed the default pthread stack size and crash the server, causing a denial of service.

h2o project reports:

When h2o receives a TLS or QUIC ClientHello containing a zero-length SNI extension, it can overrun the zero-length hostname while copying it. This can trigger a segmentation fault and cause a denial of service.

h2o project reports:

An HTTP/2 attack can combine HPACK decompression state amplification with stalled streams. Depending on server configuration, decoded header state can be retained by stalled streams, causing excessive memory use and denial of service.

https://github.com/erlang/otp/security/advisories/GHSA-6f4f-chj5-5g97 reports:

A buffer overflow error when parsing SCTP ERROR or ABORT chunks has been fixed. This could lead to stack corruption and VM crash, but ultimately with hard work by an attacker be refined into maybe even remote code execution.

https://github.com/erlang/otp/security/advisories/GHSA-xcxj-5pg2-v72j reports:

Fixed a stack overflow in ei_s_print_term in erl_interface for very large integer terms (more than 2000 hexadecimal digits long).

https://github.com/erlang/otp/security/advisories/GHSA-24cv-hwgr-37fq reports:

The FTP client in passive mode did not validate the IP address returned in the server's response, allowing a compromised or malicious server to redirect the data connection to an arbitrary host. This enables server-side request forgery (SSRF) and FTP bounce attacks.

https://github.com/erlang/otp/security/advisories/GHSA-m75x-4vwg-ggjh reports:

The HTTP client (httpc) in inets now removes Authorization, Proxy-Authorization, Cookie, Referer, and Origin headers when following a redirect to a different host or port, following the requirements of RFC 9110 section 15.4. Previously these headers were forwarded verbatim, potentially leaking credentials to unintended targets.

https://github.com/erlang/otp/security/advisories/GHSA-pv7g-pjrq-x2fh reports:

The SSH SFTP daemon's handling of SSH_FXP_READLINK returned symbolic link targets containing the server's absolute filesystem path, disclosing the backend root prefix to clients. The handler now strips the backend root prefix from symlink targets before returning them.

https://github.com/erlang/otp/security/advisories/GHSA-gp7x-mfv6-52cv reports:

Erlang distribution over TLS run with the kernel check_ip flag now properly enforces connecting nodes to be on the same LAN. Previously the constraint was not enforced.

https://github.com/erlang/otp/security/advisories/GHSA-3w6p-vwhf-wvp4 reports:

A timing-based username enumeration vulnerability during password authentication with the user_passwords option has been fixed by performing a dummy PBKDF2 computation for invalid usernames, so authentication timing no longer reveals whether a username exists.

Ack project reports:

CVE-2026-49147: filename ANSI escape sequences

CVE-2026-49146: project .ackrc -A -B -C memory exhaustion

CVE-2026-49145: project .ackrc --follow / --files-from file exfiltration

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-q49f-xg75-m9xw reports:

Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime's Winch compiler contains a vulnerability where the compilation of the table.fill instruction can result in a host panic. This means that a valid guest can be compiled with Winch, on any architecture, and cause the host to panic. This represents a denial-of-service vulnerability in Wasmtime due to guests being able to trigger a panic. The specific issue is that a historical refactoring changed how compiled code referenced tables within the table.* instructions. This refactoring forgot to update the Winch code paths associated as well, meaning that Winch was using the wrong indexing scheme. Due to the feature support of Winch the only problem that can result is tables being mixed up or nonexistent tables being used, meaning that the guest is limited to panicking the host (using a nonexistent table), or executing spec-incorrect behavior and modifying the wrong table. This vulnerability is fixed in crate versions: 36.0.7, 42.0.2, and 43.0.1.

The OpenSSL project reports:

Eighteen vulnerabilities in OpenSSL library. Highest classification High.

Chrome Releases reports:

This update includes 74 security fixes:

• [516501794] Critical CVE-2026-11628: Use after free in Ozone.
• [516674532] Critical CVE-2026-11629: Use after free in Ozone.
• [516677924] Critical CVE-2026-11630: Use after free in File Input.
• [516691130] Critical CVE-2026-11631: Use after free in Aura.
• [516707881] Critical CVE-2026-11632: Use after free in TabStrip.
• [516963272] Critical CVE-2026-11633: Use after free in Bluetooth.
• [516975148] Critical CVE-2026-11634: Use after free in Gamepad.
• [516987814] Critical CVE-2026-11635: Use after free in Bluetooth.
• [517023053] Critical CVE-2026-11636: Use after free in Autofill.
• [517040438] Critical CVE-2026-11637: Use after free in Views.
• [517047197] Critical CVE-2026-11638: Use after free in Printing.
• [517227707] Critical CVE-2026-11639: Use after free in Compositing.
• [517339758] Critical CVE-2026-11640: Integer overflow in libyuv.
• [517418936] Critical CVE-2026-11641: Use after free in Bluetooth.
• [517678820] Critical CVE-2026-11642: Use after free in Web Apps.
• [518006379] Critical CVE-2026-11643: Use after free in Proxy.
• [518043597] Critical CVE-2026-11644: Use after free in Views.
• [506689381] High CVE-2026-11645: Out of bounds memory access in V8.
• [517168239] High CVE-2026-11646: Use after free in ViewTransitions.
• [502156940] High CVE-2026-11647: Use after free in Printing.
• [506684534] High CVE-2026-11648: Use after free in FullScreen.
• [511270083] High CVE-2026-11649: Use after free in V8.
• [511279942] High CVE-2026-11650: Use after free in V8.
• [511736002] High CVE-2026-11651: Use after free in Network.
• [513156160] High CVE-2026-11652: Use after free in Extensions.
• [513321171] High CVE-2026-11653: Insufficient validation of untrusted input in Extensions.
• [513362710] High CVE-2026-11654: Use after free in CameraCapture.
• [513396305] High CVE-2026-11655: Integer overflow in Media.
• [513424000] High CVE-2026-11656: Use after free in ServiceWorker.
• [513465272] High CVE-2026-11657: Use after free in Payments.
• [513564337] High CVE-2026-11658: Insufficient validation of untrusted input in Extensions.
• [513702971] High CVE-2026-11659: Insufficient validation of untrusted input in UI.
• [513731890] High CVE-2026-11660: Insufficient validation of untrusted input in New Tab Page.
• [513748868] High CVE-2026-11661: Use after free in Views.
• [513773313] High CVE-2026-11662: Type Confusion in Bindings.
• [513820666] High CVE-2026-11663: Use after free in Skia.
• [513830374] High CVE-2026-11664: Use after free in Payments.
• [513948465] High CVE-2026-11665: Out of bounds read in Dawn.
• [514009323] High CVE-2026-11666: Insufficient validation of untrusted input in Input.
• [514671098] High CVE-2026-11667: Out of bounds read in WebRTC.
• [515419790] High CVE-2026-11668: Uninitialized Use in Codecs.
• [515429352] High CVE-2026-11669: Integer overflow in Media.
• [515469283] High CVE-2026-11670: Use after free in PDF.
• [516608438] High CVE-2026-11671: Use after free in Navigation.
• [516794471] High CVE-2026-11672: Out of bounds write in GPU.
• [516902973] High CVE-2026-11673: Use after free in InterestGroups.
• [516910450] High CVE-2026-11674: Use after free in Guest View.
• [516915337] High CVE-2026-11675: Insufficient validation of untrusted input in Skia.
• [516949298] High CVE-2026-11676: Insufficient validation of untrusted input in Dawn.
• [516979551] High CVE-2026-11677: Race in Network.
• [516986556] High CVE-2026-11678: Integer overflow in libyuv.
• [516997135] High CVE-2026-11679: Use after free in Codecs.
• [517004487] High CVE-2026-11680: Use after free in Media.
• [517050585] High CVE-2026-11681: Use after free in Ozone.
• [517103584] High CVE-2026-11682: Insufficient validation of untrusted input in Views.
• [517129549] High CVE-2026-11683: Use after free in WebCodecs.
• [517130229] High CVE-2026-11684: Insufficient policy enforcement in Network.
• [517183713] High CVE-2026-11685: Insufficient data validation in MediaCapture.
• [517247333] High CVE-2026-11686: Insufficient validation of untrusted input in Dawn.
• [517303276] High CVE-2026-11687: Use after free in Dawn.
• [517309206] High CVE-2026-11688: Object lifecycle issue in SVG.
• [517486004] High CVE-2026-11689: Insufficient validation of untrusted input in Passwords.
• [517533654] High CVE-2026-11690: Out of bounds read and write in Media.
• [517585486] High CVE-2026-11691: Insufficient validation of untrusted input in New Tab Page.
• [517607902] High CVE-2026-11692: Use after free in Read Anything.
• [517644287] High CVE-2026-11693: Inappropriate implementation in Plugins.
• [517705966] High CVE-2026-11694: Use after free in ServiceWorker.
• [517762104] High CVE-2026-11695: Inappropriate implementation in Passwords.
• [517993381] High CVE-2026-11696: Uninitialized Use in Video.
• [518105731] High CVE-2026-11697: Insufficient validation of untrusted input in UI.
• [518235412] High CVE-2026-11698: Use after free in Bluetooth.
• [518237527] High CVE-2026-11699: Use after free in Bluetooth.
• [511732085] Medium CVE-2026-11700: Use after free in Tracing.
• [516413817] Medium CVE-2026-11701: Insufficient validation of untrusted input in Guest View.

Problem Description:

When used as a stub resolver over UDP, ldns failed to verify that a received response belonged to the outstanding query. It did not check that the response source address and port matched the query destination, that the transaction ID matched, or that the question section of the response matched that of the query.

Impact:

Without these checks, an off-path attacker who cannot observe the query can forge UDP responses that ldns will accept as genuine. By injecting spoofed replies, the attacker can return arbitrary DNS data to any program that uses ldns for stub resolving, including drill(1).

Problem Description:

Multiple issues have been reported as part of this advisory with different issues affecting different OpenSSL versions and therefore different FreeBSD versions. Instead of exhaustively listing detailed writeups for each issue, please see the referenced advisory from OpenSSL.

Issues affecting FreeBSD 15.x (OpenSSL 3.5):

• CVE-2026-7383: Possible heap buffer overflow in ASN.1 string conversion
• CVE-2026-9076: Out-of-bounds read in CMS password-based decryption
• CVE-2026-34180: Heap buffer over-read in ASN.1 content parsing
• CVE-2026-34181: PKCS#12 files with PBMAC1 accepted with short HMAC keys
• CVE-2026-34182: CMS AuthEnvelopedData may accept forged messages
• CVE-2026-34183: Unbounded memory growth in the QUIC PATH_CHALLENGE handler
• CVE-2026-42764: NULL dereference in QUIC server initial packet handling
• CVE-2026-42766: Possible NULL dereference in password-based CMS decryption
• CVE-2026-42767: NULL dereference in CRMF EncryptedValue decryption
• CVE-2026-42768: Bleichenbacher oracle in CMS_decrypt() and PKCS7_decrypt()
• CVE-2026-42769: Trust-anchor substitution in CMP rootCaKeyUpdate handling
• CVE-2026-42770: FFC-DH peer validation uses attacker-supplied q
• CVE-2026-45445: AES-OCB IV ignored on the EVP_Cipher() one-shot path
• CVE-2026-45446: Empty-message tag bypass in AES-GCM-SIV and AES-SIV modes
• CVE-2026-45447: Heap use-after-free in PKCS7_verify()

Issues affecting FreeBSD 14.x (OpenSSL 3.0):

• CVE-2026-7383: Possible heap buffer overflow in ASN.1 string conversion
• CVE-2026-9076: Out-of-bounds read in CMS password-based decryption
• CVE-2026-34180: Heap buffer over-read in ASN.1 content parsing
• CVE-2026-34182: CMS AuthEnvelopedData may accept forged messages
• CVE-2026-42766: Possible NULL dereference in password-based CMS decryption
• CVE-2026-42770: FFC-DH peer validation uses attacker-supplied q
• CVE-2026-45445: AES-OCB IV ignored on the EVP_Cipher() one-shot path
• CVE-2026-45446: Empty-message tag bypass in AES-GCM-SIV and AES-SIV modes
• CVE-2026-45447: Heap use-after-free in PKCS7_verify()

Impact:

The issues include heap buffer overflows and over-reads, NULL pointer dereferences, a use-after-free, unbounded memory allocation, and several cryptographic flaws permitting message forgery, integrity bypass, or recovery of a private key.

Security impact ranges from a Denial of Service to a potential remote code execution. See the OpenSSL advisory for specific details.

Problem Description:

The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation.

Impact:

An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.

Problem Description:

Multiple vulnerabilities have been reported in Unbound. Instead of listing detailed writeups for each issue, please see the upstream advisories referenced below.

• CVE-2026-32792: Packet of death with DNSCrypt
• CVE-2026-33278: Possible remote code execution during DNSSEC validation
• CVE-2026-40622: "Ghost domain name" variant
• CVE-2026-41292: Parsing a long list of incoming EDNS options degrades performance
• CVE-2026-42534: Jostle logic bypass degrades resolution performance
• CVE-2026-42923: Degradation of service with unbounded NSEC3 hash calculations
• CVE-2026-42944: Heap overflow and crash with multiple nsid, cookie, padding EDNS options
• CVE-2026-42959: Crash during DNSSEC validation of malicious content
• CVE-2026-42960: Possible cache poisoning while following delegation
• CVE-2026-44390: Unbounded name compression causes degradation of service
• CVE-2026-44608: Use-after-free and crash in RPZ code

Impact:

The issues range from Denial of Service (DoS) through resource exhaustion or crashes to possible remote code execution during DNSSEC validation. See the upstream Unbound advisories for specific details.

Problem Description:

The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base address was chosen.

Impact:

An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.

Problem Description:

Some Arm CPUs have errata where the ordering of stores and the TLBI+DSB sequence may be incorrect. If one CPU stores to a virtual address while another CPU invalidates the translation for that address, the second CPU's TLBI+DSB may complete before the first CPU's store has been globally observed.

Impact:

This erratum may allow software to write to a previously writable location after the page table is modified to forbid writes to that location. Consequently this may allow software to write to memory owned by a higher exception level, possibly allowing software to escalate privilege to that higher exception level.

Problem Description:

The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables.

Impact:

An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.

Problem Description:

The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a stale pointer to freed memory.

Impact:

An unprivileged local user can exploit this use-after-free to escalate privileges.

Problem Description:

sigqueue(2) was marked as permitted in capability mode with the introduction of Capsicum in 2011, but the implementation of kern_sigqueue did not include a capability mode check restricting signal delivery to the calling process's own PID.

Impact:

A process in capability mode can use sigqueue(2) to send signals to any process it could signal following standard Unix permissions, bypassing the Capsicum sandbox restriction. A compromised sandboxed process could interfere with other processes, for example by sending SIGKILL or SIGSTOP. This could be any process running as the same user, or any process, for a superuser sandboxed process.

Problem Description:

The sound(4) driver contained two memory-safety errors in its mmap(2) support.

First, dsp_mmap_single() validated the requested mapping by checking the sum of the user-supplied offset and length against the buffer size. This addition could overflow, so that a large offset and length wrapped around and passed the check. The offset was then narrowed from 64 to 32 bits when converted to a buffer address, yielding a mapping that extended past the audio buffer into unrelated kernel memory. (CVE-2026-45258)

Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. (CVE-2026-49417)

Impact:

The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).

Problem Description:

The KTLS receive path decrypted each record in place, assuming that the mbufs holding received data were anonymous and safe to modify. This assumption does not hold for data placed on a socket by sendfile(2), which can reference file-backed memory directly through non-anonymous M_EXTPG pages or EXT_SFBUF mbufs. When the sender transmits such data over a loopback connection without enabling KTLS on the transmit side, the file-backed mbufs reach the receiver's decryption path unchanged. Decrypting a record in place then overwrites the backing file's page cache instead of a private copy of the data.

Impact:

An unprivileged local user who can read a file can overwrite its contents with data of their choosing by sending the file over a loopback connection on which they have enabled KTLS receive. The write modifies the page cache directly, so it bypasses file flags such as schg and is written back to disk. By overwriting a setuid binary or other trusted file, a local user can escalate privileges, potentially gaining full control of the affected system.

Problem Description:

When used to deliver a signal to a specific thread, thr_kill2(2) called p_cansignal() to determine whether the operation was permitted but did not check the result before delivering the signal. The signal was sent even when the permission check failed. The system call returned the resulting error to the caller, but by then the signal had already been delivered.

Impact:

The missing check allows an unprivileged local user who knows or can guess a target's process and thread IDs to send any signal to a process they would not normally be permitted to signal, including processes owned by other users or by root. The same check enforces jail boundaries, so a jailed process can signal processes on the host or in other jails. Thread IDs are allocated globally and sequentially, and so can be discovered by brute force with no visibility into the target.

An attacker can stop or terminate arbitrary processes, including critical system daemons, resulting in a Denial of Service (DoS).

PJUllrich reports:

The Version module parses numeric version components without length limits. Untrusted input can trigger creation of arbitrary-precision integers, causing CPU and memory exhaustion.

PJUllrich reports:

The Version module parses numeric version components without length limits. Untrusted input can trigger creation of arbitrary-precision integers, causing CPU and memory exhaustion.

The Apache httpd project reports:

See links for details.

NLnet Labs reports:

This release consolidates security fixes for issues reported over a period of time. There are fixes for:

• CVE-2026-33278: Possible remote code execution during DNSSEC validation.
• CVE-2026-42944: Heap overflow and crash with multiple nsid, cookie, padding EDNS options.
• CVE-2026-42959: Crash during DNSSEC validation of malicious content.
• CVE-2026-32792: Packet of death with DNSCrypt.
• CVE-2026-40622: "Ghost domain name" variant.
• CVE-2026-41292: Parsing a long list of incoming EDNS options degrades performance.
• CVE-2026-42534: Jostle logic bypass degrades resolution performance.
• CVE-2026-42923: Degradation of service with unbounded NSEC3 hash calculations.
• CVE-2026-42960: Possible cache poisoning attack while following delegation.
• CVE-2026-44390: Unbounded name compression in certain cases causes degradation of service.
• CVE-2026-44608: Use after free and crash in RPZ code.

R. Elliott Childre reports:

The clone() method of the identification_t class doesn't correctly handle identities that have an empty but non-NULL encoding. Both objects will point to the same location, resulting in a double-free once the second object is destroyed. This can lead to a crash and could potentially be exploitable for remote code execution. Affected are all strongSwan versions since 4.3.3.

The Weechat project reports:

See links for detail.

The Weechat project reports:

See links for detail.

Gitlab reports:

Improper Access Control issue in Duo AI workflow runners impacts GitLab EE

Denial of Service issue in Wiki impacts GitLab CE/EE

Incorrect Authorization issue in GraphQL WorkItem API impacts GitLab CE/EE

Improper Authorization issue in Duo Workflows API impacts GitLab EE

Missing Authorization issue in Operations impacts GitLab EE

Incorrect Name Resolution issue in Pipelines impacts GitLab CE/EE

Incorrect Authorization issue in certain authentication endpoints impacts GitLab CE/EE

PowerDNS Team reports:

2025-07: Internal logic flaw in cache management can lead to a denial of service in Recursor

When using views, queries sent using TCP Proxy Protocol will select the view according to the address of the proxy, rather than the address of the initial query. This can lead to wrong data being returned.

Missing escaping of special characters (such as $ or @) in DNS names received during an AXFR operation can lead to an incorrect (non-parseable) Bind backend configuration to be written, causing this backend to fail until manual operation is performed to fix the configuration.

Missing sanity checks of the answer to the initial SOA query, when running in auto-secondary mode and receiving a notification for an not-yet-known domain may cause the server to crash.

Multiple concurrency and locking defects in the GSS-TSIG code can lead to memory corruption due to accidental data structure sharing, which can in turn lead to a program crash.

Missing proper escaping of double-quote characters when computing labels will cause AXFR of a catalog zone with a member whose producer group option contains such a character to fail.

Calif security reports:

Remote DoS in mod_http2

X.Org project reports:

Multiple issues have been found in the X server and Xwayland implementations published by X.Org for which we are releasing security fixes for in xorg-server-21.1.23 and xwayland-24.1.12.

X.Org project reports:

Multiple issues have been found in the X server and Xwayland implementations published by X.Org for which we are releasing security fixes for in xorg-server-21.1.23 and xwayland-24.1.12.

Chrome Releases reports:

This update includes 151 security fixes:

• [505077859] Critical CVE-2026-9872: Out of bounds write in GPU.
• [507365348] Critical CVE-2026-9873: Use after free in Network.
• [500609038] Critical CVE-2026-9874: Use after free in Dawn.
• [507508103] Critical CVE-2026-9875: Out of bounds read in WebGL.
• [493747593] Critical CVE-2026-9876: Use after free in WebGL.
• [496445460] Critical CVE-2026-9877: Use after free in ANGLE.
• [499054245] Critical CVE-2026-9878: Use after free in ANGLE.
• [499129768] Critical CVE-2026-9879: Out of bounds write in ANGLE.
• [503615025] Critical CVE-2026-9880: Insufficient validation of untrusted input in WebGL.
• [505140741] Critical CVE-2026-9881: Use after free in Bluetooth.
• [506375217] Critical CVE-2026-9882: Integer overflow in ANGLE.
• [506477192] Critical CVE-2026-9883: Use after free in Base.
• [508289938] Critical CVE-2026-9884: Use after free in Browser.
• [508452241] Critical CVE-2026-9885: Insufficient validation of untrusted input in UI.
• [508456788] Critical CVE-2026-9886: Use after free in Base.
• [511249104] Critical CVE-2026-9887: Use after free in Proxy.
• [511715166] Critical CVE-2026-9888: Use after free in WebView.
• [511727159] Critical CVE-2026-9889: Out of bounds read and write in Dawn.
• [513135985] Critical CVE-2026-9890: Use after free in XR.
• [513508128] Critical CVE-2026-9891: Use after free in Extensions.
• [513948178] Critical CVE-2026-9892: Inappropriate implementation in Skia.
• [513972075] Critical CVE-2026-9893: Use after free in Skia.
• [507707838] High CVE-2026-9894: Use after free in GPU.
• [491685406] High CVE-2026-9895: Out of bounds read in GPU.
• [508811474] High CVE-2026-9896: Out of bounds write in V8.
• [496271580] High CVE-2026-9897: Use after free in DOM.
• [496282591] High CVE-2026-9898: Insufficient validation of untrusted input in GPU.
• [497533569] High CVE-2026-9899: Use after free in ANGLE.
• [497637277] High CVE-2026-9900: Out of bounds write in ANGLE.
• [497737770] High CVE-2026-9901: Use after free in ANGLE.
• [498205735] High CVE-2026-9902: Use after free in Accessibility.
• [498783665] High CVE-2026-9903: Insufficient validation of untrusted input in Site Isolation.
• [498804020] High CVE-2026-9904: Use after free in ANGLE.
• [498883610] High CVE-2026-9905: Use after free in Accessibility.
• [499005260] High CVE-2026-9906: Out of bounds write in GPU.
• [499091269] High CVE-2026-9907: Out of bounds read in Dawn.
• [499091328] High CVE-2026-9908: Out of bounds read in ANGLE.
• [499152771] High CVE-2026-9909: Integer overflow in Skia.
• [499176133] High CVE-2026-9910: Out of bounds memory access in ANGLE.
• [499205491] High CVE-2026-9911: Integer overflow in ANGLE.
• [499873765] High CVE-2026-9912: Inappropriate implementation in GPU.
• [500046096] High CVE-2026-9913: Inappropriate implementation in ANGLE.
• [500047428] High CVE-2026-9914: Insufficient validation of untrusted input in ANGLE.
• [500063836] High CVE-2026-9915: Heap buffer overflow in ANGLE.
• [500080303] High CVE-2026-9916: Out of bounds write in ANGLE.
• [500095304] High CVE-2026-9917: Uninitialized Use in WebGL.
• [500099471] High CVE-2026-9918: Inappropriate implementation in Tint.
• [500114058] High CVE-2026-9919: Out of bounds read in WebGL.
• [500138014] High CVE-2026-9920: Uninitialized Use in GPU.
• [500150338] High CVE-2026-9921: Uninitialized Use in WebGL.
• [500187083] High CVE-2026-9922: Use after free in GPU.
• [500393328] High CVE-2026-9923: Use after free in Skia.
• [500398345] High CVE-2026-9924: Heap buffer overflow in ANGLE.
• [500536458] High CVE-2026-9925: Use after free in ANGLE.
• [500540748] High CVE-2026-9926: Heap buffer overflow in ANGLE.
• [500540958] High CVE-2026-9927: Use after free in ANGLE.
• [501125002] High CVE-2026-9928: Out of bounds read in ANGLE.
• [501367791] High CVE-2026-9929: Inappropriate implementation in WebGL.
• [501499832] High CVE-2026-9930: Out of bounds write in Dawn.
• [501524262] High CVE-2026-9931: Use after free in GPU.
• [501563323] High CVE-2026-9932: Use after free in ANGLE.
• [501575979] High CVE-2026-9933: Use after free in Input.
• [501576946] High CVE-2026-9934: Use after free in Aura.
• [501584689] High CVE-2026-9935: Uninitialized Use in ANGLE.
• [502104354] High CVE-2026-9936: Use after free in GFX.
• [502112506] High CVE-2026-9937: Use after free in UI.
• [502300817] High CVE-2026-9938: Inappropriate implementation in V8.
• [502735235] High CVE-2026-9939: Heap buffer overflow in WebCodecs.
• [502738003] High CVE-2026-9940: Heap buffer overflow in ANGLE.
• [502812366] High CVE-2026-9941: Use after free in ANGLE.
• [503438092] High CVE-2026-9942: Uninitialized Use in ANGLE.
• [503464551] High CVE-2026-9943: Out of bounds read in WebGL.
• [503471286] High CVE-2026-9944: Uninitialized Use in ANGLE.
• [503565293] High CVE-2026-9945: Use after free in Media.
• [503596863] High CVE-2026-9946: Use after free in ANGLE.
• [503627446] High CVE-2026-9947: Use after free in XML.
• [503790201] High CVE-2026-9948: Use after free in Views.
• [503793153] High CVE-2026-9949: Use after free in Core.
• [503862359] High CVE-2026-9950: Insufficient validation of untrusted input in iOS.
• [503873388] High CVE-2026-9951: Use after free in UI.
• [503929476] High CVE-2026-9952: Use after free in WebAudio.
• [503985322] High CVE-2026-9953: Out of bounds read in ANGLE.
• [504175497] High CVE-2026-9954: Use after free in TabStrip.
• [504184408] High CVE-2026-9955: Inappropriate implementation in iOS.
• [504195132] High CVE-2026-9956: Use after free in iOS.
• [504516117] High CVE-2026-9957: Use after free in PDF.
• [504555886] High CVE-2026-9958: Use after free in PDFium.
• [504557432] High CVE-2026-9959: Race in WebRTC.
• [504573260] High CVE-2026-9960: Integer overflow in PDFium.
• [504710769] High CVE-2026-9961: Use after free in SurfaceCapture.
• [504716948] High CVE-2026-9962: Use after free in WebRTC.
• [505143241] High CVE-2026-9963: Uninitialized Use in iOS.
• [505190999] High CVE-2026-9964: Use after free in Bluetooth.
• [506377574] High CVE-2026-9965: Out of bounds write in ANGLE.
• [506388321] High CVE-2026-9966: Integer overflow in XML.
• [506414791] High CVE-2026-9967: Out of bounds write in GPU.
• [506499280] High CVE-2026-9968: Integer overflow in V8.
• [506550494] High CVE-2026-9969: Insufficient validation of untrusted input in ANGLE.
• [506653647] High CVE-2026-9970: Use after free in WebGL.
• [508448586] High CVE-2026-9971: Inappropriate implementation in iOS.
• [508463705] High CVE-2026-9972: Uninitialized Use in Gamepad.
• [509268941] High CVE-2026-9973: Out of bounds write in V8.
• [511710468] High CVE-2026-9974: Out of bounds write in GPU.
• [511719039] High CVE-2026-9975: Out of bounds read and write in ANGLE.
• [511732828] High CVE-2026-9976: Inappropriate implementation in USB.
• [511741173] High CVE-2026-9977: Insufficient validation of untrusted input in WebShare.
• [511741396] High CVE-2026-9978: Use after free in Glic.
• [511742228] High CVE-2026-9979: Insufficient validation of untrusted input in Input.
• [511776372] High CVE-2026-9980: Insufficient validation of untrusted input in Printing.
• [512995705] High CVE-2026-9981: Inappropriate implementation in Skia.
• [513001247] High CVE-2026-9982: Insufficient validation of untrusted input in ANGLE.
• [513001309] High CVE-2026-9983: Type Confusion in Skia.
• [513002543] High CVE-2026-9984: Use after free in UI.
• [513019760] High CVE-2026-9985: Insufficient validation of untrusted input in Media.
• [513028160] High CVE-2026-9986: Insufficient validation of untrusted input in OptimizationGuide.
• [513046475] High CVE-2026-9987: Insufficient validation of untrusted input in WebAppInstalls.
• [513049286] High CVE-2026-9988: Use after free in WebRTC.
• [513054053] High CVE-2026-9989: Inappropriate implementation in Media.
• [513128608] High CVE-2026-9990: Use after free in WebAppInstalls.
• [513173565] High CVE-2026-9991: Inappropriate implementation in Media.
• [513177826] High CVE-2026-9992: Use after free in Network.
• [513208588] High CVE-2026-9993: Use after free in Views.
• [513235131] High CVE-2026-9994: Use after free in Core.
• [513256572] High CVE-2026-9995: Use after free in WebXR.
• [513268100] High CVE-2026-9996: Out of bounds read in WebRTC.
• [513324041] High CVE-2026-9997: Use after free in Input.
• [513337118] High CVE-2026-9998: Integer overflow in Skia.
• [513364480] High CVE-2026-9999: Inappropriate implementation in ANGLE.
• [513505608] High CVE-2026-10000: Use after free in Passwords.
• [513505927] High CVE-2026-10001: Use after free in PerformanceManager.
• [513536416] High CVE-2026-10002: Use after free in PDFium.
• [513609324] High CVE-2026-10003: Use after free in Views.
• [513730012] High CVE-2026-10004: Insufficient validation of untrusted input in Passwords.
• [513750089] High CVE-2026-10005: Use after free in WebAppInstalls.
• [513750691] High CVE-2026-10006: Race in WebAudio.
• [513754619] High CVE-2026-10007: Use after free in SVG.
• [513768979] High CVE-2026-10008: Uninitialized Use in GPU.
• [513973560] High CVE-2026-10009: Integer overflow in Skia.
• [513995565] High CVE-2026-10010: Inappropriate implementation in Input.
• [514017326] High CVE-2026-10011: Inappropriate implementation in Skia.
• [514063977] High CVE-2026-10012: Use after free in Skia.
• [514715455] High CVE-2026-10013: Use after free in WebCodecs.
• [514742327] High CVE-2026-10014: Use after free in WebMIDI.
• [514746176] High CVE-2026-10015: Integer overflow in WTF.
• [515155946] High CVE-2026-10016: Use after free in DOM.
• [504156069] Medium CVE-2026-10017: Out of bounds read in Headless.
• [504175501] Medium CVE-2026-10018: Integer overflow in ANGLE.
• [505056913] Medium CVE-2026-10019: Integer overflow in ANGLE.
• [496565479] Medium CVE-2026-10020: Insufficient validation of untrusted input in Skia.
• [497327715] Medium CVE-2026-10021: Insufficient validation of untrusted input in USB.
• [513289241] Medium CVE-2026-10022: Type Confusion in V8.

https://go.dev/issue/78913 reports:

CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's <content> attribute. If the URL content were to insert ASCII whitespaces around the '=' rune inside of the <content> attribute, the escaper would fail to similarly escape it, leading to XSS.

If a trusted template author were to write a <script> tag containing an empty 'type' attribute or a 'type' attribute with an ASCII whitespace, the execution of the template would incorrectly escape any data passed into the <script> block.

The MariaDB project reports:

Multiple vulnerabilities in MariaDB Cluster (Galera)

Mailpit author reports:

Sibling-endpoint memory-exhaustion DoS via unbounded JSON body on /api/v1/messages, /api/v1/tags, and /api/v1/message/{id}/release

Cary Phillips reports:

[The OpenEXR 3.4.12] release addresses the following security vulnerabilities:

• CVE-2026-45696 OpenEXR ht_undo_impl heap-buffer-overflow READ via codestream/channel width mismatch in HTJ2K decode
• CVE-2026-44663 Integer overflow in HTJ2K decoder ( ht_undo_impl ) leading to heap-buffer-overflow
• OSS-Fuzz 512895184 Null-dereference WRITE in Imf_4_0::TileProcess::run_decode
• OSS-fuzz 512314697 Direct-leak in internal_exr_add_part
• OSS-fuzz 508362159 Heap-buffer-overflow in DwaCompressor_uncompress
• OSS-fuzz 507413960 Heap-buffer-overflow in generic_unpack

https://github.com/erlang/otp/security/advisories/GHSA-22cw-4ph4-6447 reports:

Erlang/OTP's TLS hostname verification implements a legacy RFC 6125 fallback that checks the Subject CommonName when the Subject Alternative Name (SAN) extension is absent, rather than following RFC 9525 which requires validation to fail without SAN. Combined with weak handling of X.509 Name Constraints, this enables man-in-the-middle attacks when an attacker controls a DNS-constrained sub-CA and can intercept network traffic, allowing forgery of certificates for unauthorized domains.

https://github.com/erlang/otp/security/advisories/GHSA-c99q-jmpx-v8qq reports:

Erlang/OTP's public_key application contains a path-validation flaw where non-CA certificates lacking keyUsage extensions can be accepted as intermediate issuers. An attacker with an end-entity certificate issued by a trusted CA can exploit this to forge arbitrary leaf certificates, allowing public_key:pkix_path_validation/3 to validate fraudulent certificate chains and potentially compromise systems relying on SSL/TLS validation.

https://github.com/erlang/otp/security/advisories/GHSA-cjxj-wj6x-3fff reports:

Erlang/OTP's public_key application fails to validate the validity period of OCSP responder certificates during response verification. An attacker possessing an expired OCSP responder's private key can forge responses that the system accepts as valid, potentially allowing acceptance of revoked TLS certificates in OCSP stapling scenarios or authentication bypass in applications using the public_key:pkix_ocsp_validate/5 API directly.

https://grafana.com/security/security-advisories/cve-2026-33375 reports:

The Grafana MSSQL data source plugin contains a logic flaw that allows a low-privileged user (Viewer) to bypass API restrictions and trigger a catastrophic Out-Of-Memory (OOM) memory exhaustion, crashing the host container.

https://grafana.com/security/security-advisories/cve-2026-28375 reports:

A testdata data-source can be used to trigger out-of-memory crashes in Grafana.

https://grafana.com/security/security-advisories/cve-2026-27880 reports:

The OpenFeature feature toggle evaluation endpoint reads unbounded values into memory, which can cause out-of-memory crashes.

https://grafana.com/security/security-advisories/cve-2026-27879 reports:

A resample query can be used to trigger out-of-memory crashes in Grafana.

https://grafana.com/security/security-advisories/cve-2026-27877 reports:

When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards. No passwords of proxied data-sources are exposed. We encourage all direct data-sources to be converted to proxied data-sources as far as possible to improve your deployments' security.

https://grafana.com/security/security-advisories/cve-2026-27876 reports:

A chained attack via SQL Expressions and a Grafana Enterprise plugin can lead to a remote arbitrary code execution impact (RCE). This is enabled by a feature in Grafana (OSS), so all users are always recommended to update to avoid future attack vectors going this path. Only instances with the sqlExpressions feature toggle enabled are vulnerable.

https://grafana.com/security/security-advisories/cve-2026-21722 reports:

Public dashboards with annotations enabled did not limit their annotation timerange to the locked timerange of the public dashboard. This means one could read the entire history of annotations visible on the specific dashboard, even those outside the locked timerange. This did not leak any annotations that would not otherwise be visible on the public dashboard.

https://grafana.com/security/security-advisories/cve-2025-41117 reports:

Stack traces in Grafana's Explore Traces view can be rendered as raw HTML, and thus inject malicious JavaScript in the browser. This would require malicious JavaScript to be entered into the stack trace field. Only datasources with the Jaeger HTTP API appear to be affected; Jaeger gRPC and Tempo do not appear affected whatsoever.

The Jellyfin project reports:

Jellyfin Server 10.11.10 fixes three security vulnerabilities:

• GHSA-f47c-m7gr-q92j: (details pending disclosure)
• GHSA-jg92-mrxq-vv75: (details pending disclosure)
• GHSA-wwwm-px48-fpvq: (details pending disclosure)

The Roundcube Webmail project reports:

See link for details. No CVE numbers available at the moment.

The traefik project releases a new version addressing a CVE:

• CVE-2026-44774 (Gateway API TraefikService backend accepts rest@internal, allowing unauthorized exposure of the REST provider)

The nginx developers report:

A heap memory buffer overflow might occur in a worker process when using a configuration with overlapping captures in ngx_http_rewrite_module, potentially resulting in arbitrary code execution (CVE-2026-9256).

Simon Tatham reports:

These features are new in PuTTY 0.84:

• Security issue: fixed a remotely triggerable double-free in RSA key exchange. (We don't know of any way it is exploitable to execute code.)
• Minor security issue: fixed a remotely triggerable crash in NIST ECDSA signature verification. (An assertion failure – definitely not exploitable to execute code.)
• Minor security issue: fixed marking of Telnet and Rlogin session data with a trust sigil after you authenticated to a proxy (possibly allowing a server to spoof a repeat proxy password prompt).

The GStreamer project reports multiple security vulnerabilities fixed in the 1.28.3 release:

Six security vulnerabilities were addressed, including:

• Bounds check errors in MXF VANC packet handling.
• Use-after-free in GStreamer core buffer value deserialization.
• Out-of-bounds read in MXF demuxer temporal offset check.
• Out-of-bounds write in H.266/VVC parser when parsing PPS tile slices.
• Insufficient validation in MOV/MP4 demuxer uncompressed video handling.
• Out-of-bounds reads in MPEG PS PES header parsing.

These could lead to application crashes, memory corruption, or potentially arbitrary code execution.

The GStreamer project reports multiple security vulnerabilities fixed in the 1.28.2 release:

Several security vulnerabilities were addressed, including:

• H.264 video parser NULL pointer dereference when freeing SPS/MVC data.
• Integer overflows in the AV1 LEB128 parser, H.266/VVC video parser, and WAV parser cue handling.
• Heap buffer overflow in the Matroska demuxer.
• Assertion failures in the FLV demuxer on corrupted streams.
• NULL-pointer dereferences in the mDVDsub subtitle parser.
• Multiple out-of-bounds reads and writes in the MOV/MP4 demuxer audio channel layout parsing.
• Denial of service in SRT/WebVTT parser

These could lead to application crashes, memory exhaustion, or potentially arbitrary code execution.

Qt qtwebengine-chromium repo reports:

Backports for 262 security bugs in Chromium:

• CVE-2025-13223: Type Confusion in V8
• CVE-2025-13224: Type Confusion in V8
• CVE-2025-13630: Type Confusion in V8
• CVE-2025-13632: Inappropriate implementation in DevTools
• CVE-2025-13634: Inappropriate implementation in Downloads
• CVE-2025-13721: Race in v8
• CVE-2025-14766: Out of bounds read and write in V8
• CVE-2026-0628: Insufficient policy enforcement in WebView tag
• CVE-2026-0899: Out of bounds memory access in V8
• CVE-2026-0902: Inappropriate implementation in V8
• CVE-2026-0905: Insufficient policy enforcement in Network
• CVE-2026-1220: Description pending NVD publication
• CVE-2026-1861: Heap buffer overflow in libvpx
• CVE-2026-2314: Heap buffer overflow in Codecs
• CVE-2026-2315: Inappropriate implementation in WebGPU
• CVE-2026-2316: Insufficient policy enforcement in Frames
• CVE-2026-2317: Inappropriate implementation in Animation
• CVE-2026-2319: Race in DevTools
• CVE-2026-2320: Inappropriate implementation in File input
• CVE-2026-2441: Use after free in CSS
• CVE-2026-2648: Heap buffer overflow in PDFium
• CVE-2026-2649: Integer overflow in V8
• CVE-2026-2650: Heap buffer overflow in Media
• CVE-2026-3061: Out of bounds read in Media
• CVE-2026-3062: Out of bounds read and write in Tint
• CVE-2026-3063: Inappropriate implementation in DevTools
• CVE-2026-3536: Integer overflow in ANGLE
• CVE-2026-3537: Object lifecycle issue in PowerVR
• CVE-2026-3538: Integer overflow in Skia
• CVE-2026-3539: Object lifecycle issue in DevTools
• CVE-2026-3540: Inappropriate implementation in WebAudio
• CVE-2026-3541: Inappropriate implementation in CSS
• CVE-2026-3542: Inappropriate implementation in WebAssembly
• CVE-2026-3543: Inappropriate implementation in V8
• CVE-2026-3544: Heap buffer overflow in WebCodecs
• CVE-2026-3545: Insufficient data validation in Navigation
• CVE-2026-3909: Out of bounds write in Skia
• CVE-2026-3910: Inappropriate implementation in V8
• CVE-2026-3919: Use after free in Extensions
• CVE-2026-3921: Use after free in TextEncoding
• CVE-2026-3922: Use after free in MediaStream
• CVE-2026-3923: Use after free in WebMIDI
• CVE-2026-3924: use after free in WindowDialog
• CVE-2026-3926: Out of bounds read in V8
• CVE-2026-3929: Side-channel information leakage in ResourceTiming
• CVE-2026-3931: Heap buffer overflow in Skia
• CVE-2026-3934: Insufficient policy enforcement in ChromeDriver
• CVE-2026-3938: Insufficient policy enforcement in Clipboard
• CVE-2026-3940: Insufficient policy enforcement in DevTools
• CVE-2026-3941: Insufficient policy enforcement in DevTools
• CVE-2026-3942: Incorrect security UI in PictureInPicture
• CVE-2026-4440: Out of bounds read and write in WebGL
• CVE-2026-4441: Use after free in Base
• CVE-2026-4442: Heap buffer overflow in CSS
• CVE-2026-4443: Heap buffer overflow in WebAudio
• CVE-2026-4444: Stack buffer overflow in WebRTC
• CVE-2026-4445: Use after free in WebRTC
• CVE-2026-4446: Use after free in WebRTC
• CVE-2026-4448: Heap buffer overflow in ANGLE
• CVE-2026-4449: Use after free in Blink
• CVE-2026-4450: Out of bounds write in V8
• CVE-2026-4451: Insufficient validation of untrusted input in Navigation
• CVE-2026-4452: Integer overflow in ANGLE
• CVE-2026-4453: Integer overflow in Dawn
• CVE-2026-4454: Use after free in Network
• CVE-2026-4455: Heap buffer overflow in PDFium
• CVE-2026-4457: Type Confusion in V8
• CVE-2026-4458: Use after free in Extensions
• CVE-2026-4459: Out of bounds read and write in WebAudio
• CVE-2026-4460: Out of bounds read in Skia
• CVE-2026-4462: Out of bounds read in Blink
• CVE-2026-4463: Heap buffer overflow in WebRTC
• CVE-2026-4464: Integer overflow in ANGLE
• CVE-2026-4674: Out of bounds read in CSS
• CVE-2026-4675: Heap buffer overflow in WebGL
• CVE-2026-4677: Out of bounds read in WebAudio
• CVE-2026-4679: Integer overflow in Fonts
• CVE-2026-5272: Heap buffer overflow in GPU
• CVE-2026-5273: Use after free in CSS
• CVE-2026-5274: Integer overflow in Codecs
• CVE-2026-5275: Heap buffer overflow in ANGLE
• CVE-2026-5276: Insufficient policy enforcement in WebUSB
• CVE-2026-5277: Integer overflow in ANGLE
• CVE-2026-5279: Object corruption in V8
• CVE-2026-5280: Use after free in WebCodecs
• CVE-2026-5281: Use after free in Dawn
• CVE-2026-5282: Out of bounds read in WebCodecs
• CVE-2026-5283: Inappropriate implementation in ANGLE
• CVE-2026-5284: Use after free in Dawn
• CVE-2026-5285: Use after free in WebGL
• CVE-2026-5287: Use after free in PDF
• CVE-2026-5289: Use after free in Navigation
• CVE-2026-5290: Use after free in Compositing
• CVE-2026-5291: Inappropriate implementation in WebGL
• CVE-2026-5292: Out of bounds read in WebCodecs
• CVE-2026-5860: Use after free in WebRTC
• CVE-2026-5861: Use after free in V8
• CVE-2026-5862: Inappropriate implementation in V8
• CVE-2026-5863: Inappropriate implementation in V8
• CVE-2026-5865: Type Confusion in V8
• CVE-2026-5866: Use after free in Media
• CVE-2026-5868: Heap buffer overflow in ANGLE
• CVE-2026-5870: Integer overflow in Skia
• CVE-2026-5871: Type Confusion in V8
• CVE-2026-5872: Use after free in Blink
• CVE-2026-5873: Out of bounds read and write in V8
• CVE-2026-5875: Policy bypass in Blink
• CVE-2026-5876: Side-channel information leakage in Navigation
• CVE-2026-5877: Use after free in Navigation
• CVE-2026-5878: Incorrect security UI in Blink
• CVE-2026-5879: Insufficient validation of untrusted input in ANGLE
• CVE-2026-5880: Incorrect security UI in browser UI
• CVE-2026-5882: Incorrect security UI in Fullscreen
• CVE-2026-5883: Use after free in Media
• CVE-2026-5884: Insufficient validation of untrusted input in Media
• CVE-2026-5885: Insufficient validation of untrusted input in WebML
• CVE-2026-5886: Out of bounds read in WebAudio
• CVE-2026-5888: Uninitialized Use in WebCodecs
• CVE-2026-5889: Cryptographic Flaw in PDFium
• CVE-2026-5890: Race in WebCodecs
• CVE-2026-5891: Insufficient policy enforcement in browser UI
• CVE-2026-5893: Race in V8
• CVE-2026-5894: Inappropriate implementation in PDF
• CVE-2026-5896: Policy bypass in Audio
• CVE-2026-5899: Incorrect security UI in History Navigation
• CVE-2026-5900: Policy bypass in Downloads
• CVE-2026-5901: Policy bypass in DevTools
• CVE-2026-5903: Policy bypass in IFrameSandbox
• CVE-2026-5904: Use after free in V8
• CVE-2026-5907: Insufficient data validation in Media
• CVE-2026-5908: Integer overflow in Media
• CVE-2026-5909: Integer overflow in Media
• CVE-2026-5910: Integer overflow in Media
• CVE-2026-5911: Policy bypass in ServiceWorkers
• CVE-2026-5912: Integer overflow in WebRTC
• CVE-2026-5913: Out of bounds read in Blink
• CVE-2026-5914: Type Confusion in CSS
• CVE-2026-5915: Insufficient validation of untrusted input in WebML
• CVE-2026-5918: Inappropriate implementation in Navigation
• CVE-2026-5919: Insufficient validation of untrusted input in WebSockets
• CVE-2026-6296: Heap buffer overflow in ANGLE
• CVE-2026-6297: Use after free in Proxy
• CVE-2026-6298: Heap buffer overflow in Skia
• CVE-2026-6299: Use after free in Prerender
• CVE-2026-6300: Use after free in CSS
• CVE-2026-6301: Type Confusion in Turbofan
• CVE-2026-6302: Use after free in Video
• CVE-2026-6303: Use after free in Codecs
• CVE-2026-6304: Use after free in Graphite
• CVE-2026-6305: Heap buffer overflow in PDFium
• CVE-2026-6306: Heap buffer overflow in PDFium
• CVE-2026-6307: Type Confusion in Turbofan
• CVE-2026-6308: Out of bounds read in Media
• CVE-2026-6309: Use after free in Viz
• CVE-2026-6311: Uninitialized Use in Accessibility
• CVE-2026-6312: Insufficient policy enforcement in Passwords
• CVE-2026-6313: Insufficient policy enforcement in CORS
• CVE-2026-6314: Out of bounds write in GPU
• CVE-2026-6316: Use after free in Forms
• CVE-2026-6359: Use after free in Video
• CVE-2026-6360: Use after free in FileSystem
• CVE-2026-6361: Heap buffer overflow in PDFium
• CVE-2026-6362: Use after free in Codecs
• CVE-2026-6363: Type Confusion in V8
• CVE-2026-6364: Out of bounds read in Skia
• CVE-2026-6919: Use after free in DevTools
• CVE-2026-6920: Out of bounds read in GPU
• CVE-2026-7333: Use after free in GPU
• CVE-2026-7335: Use after free in media
• CVE-2026-7336: Use after free in WebRTC
• CVE-2026-7339: Heap buffer overflow in WebRTC
• CVE-2026-7340: Integer overflow in ANGLE
• CVE-2026-7341: Use after free in WebRTC
• CVE-2026-7342: Use after free in WebView
• CVE-2026-7343: Use after free in Views
• CVE-2026-7344: Use after free in Accessibility
• CVE-2026-7345: Insufficient validation of untrusted input in Feedback
• CVE-2026-7346: Inappropriate implementation in Tint
• CVE-2026-7348: Use after free in Codecs
• CVE-2026-7349: Use after free in Cast
• CVE-2026-7350: Use after free in WebMIDI
• CVE-2026-7351: Race in MHTML
• CVE-2026-7353: Heap buffer overflow in Skia
• CVE-2026-7354: Out of bounds read and write in Angle
• CVE-2026-7355: Use after free in Media
• CVE-2026-7356: Use after free in Navigation
• CVE-2026-7357: Use after free in GPU
• CVE-2026-7359: Use after free in ANGLE
• CVE-2026-7360: Insufficient validation of untrusted input in Compositing
• CVE-2026-7363: Use after free in Canvas
• CVE-2026-7899: Out of bounds read and write in V8
• CVE-2026-7900: Heap buffer overflow in ANGLE
• CVE-2026-7901: Use after free in ANGLE
• CVE-2026-7902: Out of bounds memory access in V8
• CVE-2026-7903: Integer overflow in ANGLE
• CVE-2026-7904: Out of bounds read in Fonts
• CVE-2026-7906: Use after free in SVG
• CVE-2026-7907: Use after free in DOM
• CVE-2026-7908: Use after free in Fullscreen
• CVE-2026-7910: Use after free in Views
• CVE-2026-7912: Integer overflow in GPU
• CVE-2026-7914: Type Confusion in Accessibility
• CVE-2026-7916: Insufficient data validation in InterestGroups
• CVE-2026-7917: Use after free in Fullscreen
• CVE-2026-7918: Use after free in GPU
• CVE-2026-7919: Use after free in Aura
• CVE-2026-7920: Use after free in Skia
• CVE-2026-7921: Use after free in Passwords
• CVE-2026-7922: Use after free in ServiceWorker
• CVE-2026-7923: Out of bounds write in Skia
• CVE-2026-7924: Uninitialized Use in Dawn
• CVE-2026-7926: Use after free in PresentationAPI
• CVE-2026-7927: Type Confusion in Runtime
• CVE-2026-7929: Use after free in MediaRecording
• CVE-2026-7933: Out of bounds read in WebCodecs
• CVE-2026-7935: Inappropriate implementation in Speech
• CVE-2026-7937: Insufficient policy enforcement in DevTools
• CVE-2026-7938: Use after free in CSS
• CVE-2026-7940: Use after free in V8
• CVE-2026-7942: Integer overflow in ANGLE
• CVE-2026-7944: Insufficient validation of untrusted input in Persistent Cache
• CVE-2026-7945: Insufficient validation of untrusted input in COOP
• CVE-2026-7946: Insufficient policy enforcement in WebUI
• CVE-2026-7947: Insufficient validation of untrusted input in Network
• CVE-2026-7949: Out of bounds read in Skia
• CVE-2026-7950: Out of bounds read and write in GFX
• CVE-2026-7951: Out of bounds write in WebRTC
• CVE-2026-7954: Race in Shared Storage
• CVE-2026-7955: Uninitialized Use in GPU
• CVE-2026-7956: Use after free in Navigation
• CVE-2026-7957: Out of bounds write in Media
• CVE-2026-7959: Inappropriate implementation in Navigation
• CVE-2026-7963: Inappropriate implementation in ServiceWorker
• CVE-2026-7964: Insufficient validation of untrusted input in FileSystem
• CVE-2026-7965: Insufficient validation of untrusted input in DevTools
• CVE-2026-7967: Insufficient validation of untrusted input in Navigation
• CVE-2026-7968: Insufficient validation of untrusted input in CORS
• CVE-2026-7969: Integer overflow in Network
• CVE-2026-7971: Inappropriate implementation in ORB
• CVE-2026-7972: Uninitialized Use in GPU
• CVE-2026-7973: Integer overflow in Dawn
• CVE-2026-7974: Use after free in Blink
• CVE-2026-7975: Use after free in DevTools
• CVE-2026-7976: Use after free in Views
• CVE-2026-7977: Inappropriate implementation in Canvas
• CVE-2026-7980: Use after free in WebAudio
• CVE-2026-7982: Uninitialized Use in WebCodecs
• CVE-2026-7983: Out of bounds read in Dawn
• CVE-2026-7985: Use after free in GPU
• CVE-2026-7986: Insufficient policy enforcement in Autofill
• CVE-2026-7987: Use after free in WebRTC
• CVE-2026-7988: Type Confusion in WebRTC
• CVE-2026-7989: Insufficient data validation in DataTransfer
• CVE-2026-7991: Use after free in UI
• CVE-2026-7993: Insufficient validation of untrusted input in Payments
• CVE-2026-7996: Insufficient validation of untrusted input in SSL
• CVE-2026-7998: Insufficient validation of untrusted input in Dialog
• CVE-2026-7999: Inappropriate implementation in V8
• CVE-2026-8002: Use after free in Audio
• CVE-2026-8003: Insufficient validation of untrusted input in TabGroups
• CVE-2026-8004: Insufficient policy enforcement in DevTools
• CVE-2026-8007: Insufficient validation of untrusted input in Cast

The rsync project reports:

Six CVEs are fixed in this release. All six are assigned by VulnCheck as CNA. Affected versions are 3.4.2 and earlier in every case.

In addition to the six CVE fixes, this release adds defence-in-depth hardening on several adjacent paths: bounded wire-supplied counts and lengths in flist/io/acls/xattrs, a guard against length underflow in cumulative snprintf() callers, a parent block-index bounds check on the receiver, a NULL check in read_delay_line(), a lower ceiling on MAX_WIRE_DEL_STAT to avoid signed-int overflow in the read_del_stats() accumulator, rejection of hyphen-prefixed remote-shell hostnames (defence-in-depth against argv-injection in tooling that forwards untrusted input into the hostspec position; reported by Aisle Research via Michal Ruprich), and a NULL-check on localtime_r() in timestring() to keep a malicious server from crashing the client by advertising a file with an out-of-range modtime.

Problem Description:

In the case of the cap_net service, when a key present in the old limit was omitted from the new limit, the missing key was treated as "allow any" instead of being rejected.

Impact:

In certain scenarios, an application that had previously restricted a subset of network operations could ask for a new limit that extended the permissions of the process.

Problem Description:

When bsdinstall or bsdconfig are prompted to scan for nearby Wi-Fi networks, they build up a list of network names and use bsddialog(1) to prompt the user to select a network. This is implemented using a shell script, and the code which handled network names was not careful to prevent expansion by the shell. As a result, a suitably crafted network name can be used to execute commands via a subshell.

Impact:

The problem can be exploited to execute code as root on the system running bsdinstall or bsdconfig. The attacker would need to create an access point with a specially crafted name and be within range of a Wi-Fi scan. Note that bsdinstall and bsdconfig are vulnerable as soon as the user prompts them to scan for nearby networks; they do not need to actually select the malicious network.

Problem Description:

libcasper(3) communicates with helper processes via UNIX domain sockets, and uses the select(2) system call to wait for data to become available. However, it does not verify that its socket descriptor fits within select(2)'s descriptor set size limit of FD_SETSIZE (1024).

Impact:

An attacker able to cause an application using libcasper(3) to allocate large file descriptors, e.g., by opening many descriptors and executing a program which is not careful to close them upon startup, may trigger stack corruption. If the target application runs with setuid root privileges, this could be used to escalate local privileges.

Problem Description:

ptrace(PT_SC_REMOTE) failed to properly validate parameters for the syscall(2) and __syscall(2) meta-system calls. As a result, a user with the ability to debug a process may trigger arbitrary code execution in the kernel, even if the target process has no special privileges.

Impact:

The missing validation allows an unprivileged local user to escalate privileges, potentially gaining full control of the affected system.

Problem Description:

When a fusefs file system implements extended attributes, the kernel may send a FUSE_LISTXATTR message to the userspace daemon to retrieve the list of extended attributes for a given file. The FUSE protocol requires the daemon to return a packed list of NUL-terminated strings. The fusefs kernel module calls strlen() on this daemon-supplied buffer without first verifying that the entire list is NUL-terminated.

Impact:

If a malicious daemon sends a non-NUL-terminated list, the fusefs kernel module may read beyond the end of one heap-allocated buffer and potentially write beyond the end of a second buffer. A malicious daemon could disclose up to 253 bytes of kernel heap memory, or it could inject up to 250 attacker-controlled bytes into unallocated kernel heap space.

Problem Description:

A file descriptor can be closed while a thread is blocked in a poll(2) or select(2) call waiting for that descriptor. Because the blocked thread does not hold a reference to the underlying object, this closure may result in the object being freed while the thread remains blocked. In this situation, the kernel must remove the blocked thread from the per-object wait queue prior to freeing the object.

In the case of some file descriptor types, the kernel failed to unlink blocked threads from the object before freeing it. When the blocked thread is subsequently woken, it accesses memory that has already been freed resulting in a use-after-free vulnerability.

Impact:

The use-after-free vulnerability may be triggered by an unprivileged local user and can be exploited to obtain superuser privileges.

Problem Description:

The setcred(2) system call is only available to privileged users. However, before the privilege level of the caller is checked, the user-supplied list of supplementary groups is copied into a fixed-size kernel stack buffer without first validating its length. If the supplied list exceeds the capacity of that buffer, a stack buffer overflow occurs.

Impact:

Because the bounds check on the supplementary groups list occurs after the kernel stack buffer has already been written, an unprivileged local user may trigger the overflow without holding any special privilege. Successful exploitation may allow an attacker to execute arbitrary code in the context of the kernel, allowing an unprivileged local user to gain elevated privileges on the affected system.

The nginx project reports:

nginx 1.31.0 fixes multiple security issues affecting HTTP/2 proxying, rewrite handling, SCGI/uWSGI response handling, charset conversion, HTTP/3 connection migration, and OCSP resolver response processing.

Oracle reports:

See linked CVE's for details.

The MariaDB project reports:

See linked CVE's for details.

Vinyl Development Team reports:

A deficiency in HTTP/2 request parsing can be exploited to launch a backend request desync attack (request smuggling), which in turn can be used for cache poisoning, authentication bypass or possibly even information disclosure and manipulation.

The PostgreSQL project reports:

Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice.

Integer wraparound in multiple PostgreSQL server features allows an application input provider to cause the server to undersize an allocation and write out-of-bounds. This results in a segmentation fault.

Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server memory, via crafted timezone zones.

Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implicitly trusts the origin superuser, due to features like shared_preload_libraries. Hence, the attack has practical implications only if one takes relevant action between these commands and server start, like moving the files to a different VM or snapshotting the VM.

SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pg_createsubscriber next runs. Versions before PostgreSQL 17 are unaffected.

PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory. Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like gets(), PQfn(..., result_is_int=0, ...) stores arbitrary-length, server-determined data into a buffer of unspecified size. Because both the \lo_export command in psql and pg_dump call lo_read(), the server superuser can overwrite pg_dump or psql stack memory.

PostgreSQL discloses MD5-hashed passwords via covert timing channel. Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier.

PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion. Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX socket to achieve sustained denial of service. If SSL and GSS are both disabled, an attacker can do the same via access to a PostgreSQL TCP socket.

PostgreSQL pg_restore_attribute_stats accepts values that cause query planning to read past end of stats array. Buffer over-read in PostgreSQL function pg_restore_attribute_stats() accepts array values of unmatched length, which causes query planning to read past end of one array. This allows a table maintainer to infer memory values past that array end. Versions before PostgreSQL 18 are unaffected.

PostgreSQL refint allows stack buffer overflow and SQL injection. Stack buffer overflow in PostgreSQL module refint allows an unprivileged database user to execute arbitrary code as the operating system user running the database. A distinct attack is possible if the application declares a user-controlled column as a refint cascade primary key and facilitates user-controlled updates to that column. In that case, a SQL injection allows a primary key update value provider to execute arbitrary SQL as the database user performing the primary key update.

PostgreSQL REFRESH PUBLICATION allows SQL injection via table name. SQL injection in PostgreSQL logical replication ALTER SUBSCRIPTION ... REFRESH PUBLICATION allows a subscriber table creator to execute arbitrary SQL with the subscription's publication-side credentials. The attack takes effect at the next REFRESH PUBLICATION. Versions before PostgreSQL 16 are unaffected.

nginx development team reports:

When using the "proxy_set_body" directive, an attacker might inject data in the proxied request to an HTTP/2 backend

A heap memory buffer overflow might occur in a worker process while handling a specially crafted request by ngx_http_rewrite_module, potentially resulting in arbitrary code execution

A heap memory buffer overread might occur in a worker process while handling a specially crafted response by ngx_http_scgi_module or ngx_http_uwsgi_module, allowing an attacker to cause a disclosure of worker process memory or segmentation fault in a worker process

A heap memory buffer overread might occur in a worker process while handling a specially sent response with decoding from UTF-8 via the "charset_map" directive, allowing an attacker to cause a limited disclosure of worker proccess memory or segmentation fault in a worker process

When using HTTP/3, processing of connection migration might cause new QUIC streams to receive a new client address before validation, allowing an attacker to cause address spoofing

use-after-free might occur during DNS server response processing if the "ssl_ocsp" directive was used, allowing an attacker to cause worker process memory corruption or segmentation fault in a worker process

Mailpit author reports:

Set a default 50MB per message limit to prevent DoS via unlimited SMTP DATA and /api/v1/send body sizes (GHSA-fpxj-m5q8-fphw)

Include CGNAT (Carrier-Grade NAT) in internal IP checks (GHSA-j3fj-qppj-fmmc)

Block internal IP access by default in HTML check (GHSA-j3fj-qppj-fmmc)

Fix for path traversal & arbitrary file write in mailpit dump --http <instance> via attacker-controlled message IDs (GHSA-qx5x-85p8-vg4j)

Fix concurrent map read & write in proxy CSS rewriter (GHSA-w4vj-r5pg-3722)

https://github.com/pypa/setuptools/security/advisories/GHSA-5rjg-fvgr-3xxf reports:

setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. A path traversal vulnerability in `PackageIndex` is present in setuptools prior to version 78.1.1. An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to remote code execution depending on the context.

Gitlab reports:

Cross-site Scripting issue in Analytics dashboard chart rendering impacts GitLab EE

Cross-site Scripting issue in global search impacts GitLab CE/EE

Cross-site Scripting issue in Duo Agent output rendering impacts GitLab EE

Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE

Denial of Service issue in CI/CD job update API impacts GitLab CE/EE

Denial of Service issue in Duo Workflows API impacts GitLab CE/EE

Denial of Service issue in internal API endpoints impacts GitLab CE/EE

Improper Authorization issue in GraphQL token scope enforcement impacts GitLab CE/EE

Denial of Service issue in Insights Configuration impacts GitLab EE

Access Control issue in Issues API impacts GitLab CE/EE

Denial of Service issue in direct transfer CSV parser impacts GitLab CE/EE

CSRF issue in JiraConnect subscriptions impacts GitLab CE/EE

Confused Deputy issue in Jira integration impacts GitLab CE/EE

Cross-site Scripting issue in Banzai markdown sanitizer impacts GitLab CE/EE

Cross-site Scripting issue in achievement email notifications impacts GitLab CE/EE

Access Control issue in Helm package upload impacts GitLab CE/EE

Improper Access Control issue in NuGet Symbol Server impacts GitLab CE/EE

Improper Access Control issue in Container Registry protected tags impacts GitLab CE/EE

Missing Authorization issue in group user search impacts GitLab CE/EE

Improper Access Control issue in code owner approval rules impacts GitLab EE

Access Control issue in PyPI Package Protection Rules impacts GitLab CE/EE

Improper Access Control issue in issue links API impacts GitLab CE/EE

Server-Side Request Forgery issue in virtual registry redirect handler impacts GitLab EE

Access Control issue in GraphQL approval rule mutations impacts GitLab EE

Missing Authorization issue in Security Policy Project Reassignment impacts GitLab EE

Wojtulewicz of Corelight reports:

A specially-crafted series of MIME headers sent via SMTP or HTTP could cause Zeek to use large amounts of memory and potentially crash.

Simon Kelley reports:

Today, 11th May 2026 CERT is releasing a set of six CVEs for serious security vulnerabilities in dnsmasq. These are all long-standing bugs which apply to pretty much all non-ancient versions.

Christopher Cullen and Molly Jaconski write, in Vulnerability Note VU#471747:

CVE-2026-2291

dnsmasq's extract_name() function can be abused to cause a heap buffer overflow, enabling an attacker to inject false DNS cache entries. This could cause DNS queries to be redirected to attacker-controlled IP addresses or result in a Denial of Service (DoS).

CVE-2026-4890

An infinite-loop flaw in the DNSSEC validation of dnsmasq allows remote attackers to cause Denial of Service (DoS) conditions via a crafted DNS packet.

CVE-2026-4891

A heap-based out-of-bounds read vulnerability in the DNSSEC validation of dnsmasq allows remote attackers to leak memory information via a crafted DNS packet.

CVE-2026-4892

A heap-based out-of-bounds write vulnerability in the DHCPv6 implementation of dnsmasq allows local attackers to execute arbitrary code with root privileges via a crafted DHCPv6 packet.

CVE-2026-4893

An information disclosure vulnerability in dnsmasq allows remote attackers to bypass source checks via a crafted DNS packet containing RFC 7871 client-subnet information.

CVE-2026-5172

A buffer overflow vulnerability in dnsmasq’s extract_addresses() function allows attackers to trigger a heap out-of-bounds read and crash dnsmasq by exploiting a malformed DNS response.

NIST reports:

Postorius through 1.3.13 does not escape HTML in the message subject when rendering it in the Held messages pop-up, as exploited in the wild in May 2026.

Expat 2.8.1 was released yesterday. The key motivation for cutting a release and doing so now was:

Fixing vulnerability CVE-2026-45186 that allows easy denial of service.

See also https://github.com/libexpat/libexpat/pull/1216

https://git.kernel.org/pub/scm/utils/dash/dash.git/commit/?id=0034bfe185d3d875cebace8cb3ca5c9dabf9e0f3 reports:

Division and remainder currently guard against division by zero, but not against the signed overflow case INTMAX_MIN / -1. On affected systems this can trigger SIGFPE during arithmetic expansion.

https://bugzilla.mozilla.org/show_bug.cgi?id=2035939 reports:

Other issue in the WebRTC component.

https://www.mozilla.org/en-US/security/advisories/mfsa2026-40/ reports:

Memory safety bugs present in Firefox 150.0.1. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

https://www.mozilla.org/en-US/security/advisories/mfsa2026-40/ reports:

Memory safety bugs. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

https://bugzilla.mozilla.org/show_bug.cgi?id=2029301 reports:

Incorrect boundary conditions in the Audio/Video: Playback component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2034352 reports:

Use-after-free in the DOM: Networking component.

Chrome Releases reports:

This update includes 127 security fixes:

Critical:

• [493747582] CVE-2026-7896: Integer overflow in Blink.
• [504069514] CVE-2026-7897: Use after free in Mobile.
• [504587882] CVE-2026-7898: Use after free in Chromoting.

High:

• [505481948] CVE-2026-7899: Out of bounds read and write in V8.
• [496503799] CVE-2026-7900: Heap buffer overflow in ANGLE.
• [497724490] CVE-2026-7901: Use after free in ANGLE.
• [502030575] CVE-2026-7902: Out of bounds memory access in V8.
• [491760376] CVE-2026-7903: Integer overflow in ANGLE.
• [492350406] CVE-2026-7904: Out of bounds read in Fonts.
• [495259842] CVE-2026-7905: Insufficient validation of untrusted input in Media.
• [496284584] CVE-2026-7906: Use after free in SVG.
• [496292089] CVE-2026-7907: Use after free in DOM.
• [497436531] CVE-2026-7908: Use after free in Fullscreen.
• [497437113] CVE-2026-7909: Inappropriate implementation in ServiceWorker.
• [497543810] CVE-2026-7910: Use after free in Views.
• [497548912] CVE-2026-7911: Use after free in Aura.
• [497639714] CVE-2026-7912: Integer overflow in GPU.
• [497936728] CVE-2026-7913: Insufficient policy enforcement in DevTools.
• [498401609] CVE-2026-7914: Type Confusion in Accessibility.
• [498454478] CVE-2026-7915: Insufficient data validation in DevTools.
• [498720754] CVE-2026-7916: Insufficient data validation in InterestGroups.
• [498752242] CVE-2026-7917: Use after free in Fullscreen.
• [498780188] CVE-2026-7918: Use after free in GPU.
• [498832921] CVE-2026-7919: Use after free in Aura.
• [498989348] CVE-2026-7920: Use after free in Skia.
• [499062376] CVE-2026-7921: Use after free in Passwords.
• [499449324] CVE-2026-7922: Use after free in ServiceWorker.
• [500080194] CVE-2026-7923: Out of bounds write in Skia.
• [500087204] CVE-2026-7924: Uninitialized Use in Dawn.
• [501833981] CVE-2026-7925: Use after free in Chromoting.
• [502249087] CVE-2026-7926: Use after free in PresentationAPI.
• [502830119] CVE-2026-7927: Type Confusion in Runtime.
• [504612429] CVE-2026-7928: Use after free in WebRTC.
• [504660052] CVE-2026-7929: Use after free in MediaRecording.

Medium:

• [434825208] CVE-2026-7930: Insufficient validation of untrusted input in Cookies.
• [474338157] CVE-2026-7931: Insufficient validation of untrusted input in iOS.
• [481634116] CVE-2026-7932: Insufficient policy enforcement in Downloads.
• [488585490] CVE-2026-7933: Out of bounds read in WebCodecs.
• [489023922] CVE-2026-7934: Insufficient validation of untrusted input in Popup Blocker.
• [489624550] CVE-2026-7935: Inappropriate implementation in Speech.
• [490485402] CVE-2026-7936: Object lifecycle issue in V8.
• [491766258] CVE-2026-7937: Insufficient policy enforcement in DevTools.
• [492735384] CVE-2026-7938: Use after free in CSS.
• [492963096] CVE-2026-7939: Inappropriate implementation in SanitizerAPI.
• [493631402] CVE-2026-7940: Use after free in V8.
• [493955234] CVE-2026-7941: Insufficient validation of untrusted input in Mobile.
• [495363705] CVE-2026-7942: Integer overflow in ANGLE.
• [495373657] CVE-2026-7943: Insufficient validation of untrusted input in ANGLE.
• [495783187] CVE-2026-7944: Insufficient validation of untrusted input in Persistent Cache.
• [495802788] CVE-2026-7945: Insufficient validation of untrusted input in COOP.
• [496016840] CVE-2026-7946: Insufficient policy enforcement in WebUI.
• [496169594] CVE-2026-7947: Insufficient validation of untrusted input in Network.
• [496193452] CVE-2026-7948: Race in Chromoting.
• [496206134] CVE-2026-7949: Out of bounds read in Skia.
• [496259890] CVE-2026-7950: Out of bounds read and write in GFX.
• [496266456] CVE-2026-7951: Out of bounds write in WebRTC.
• [496279876] CVE-2026-7952: Insufficient policy enforcement in Extensions.
• [496379792] CVE-2026-7953: Insufficient validation of untrusted input in Omnibox.
• [496380960] CVE-2026-7954: Race in Shared Storage.
• [496441232] CVE-2026-7955: Uninitialized Use in GPU.
• [496463315] CVE-2026-7956: Use after free in Navigation.
• [496607380] CVE-2026-7957: Out of bounds write in Media.
• [496632973] CVE-2026-7958: Inappropriate implementation in ServiceWorker.
• [496645205] CVE-2026-7959: Inappropriate implementation in Navigation.
• [497007825] CVE-2026-7960: Race in Speech.
• [497008295] CVE-2026-7961: Insufficient validation of untrusted input in Permissions.
• [497081987] CVE-2026-7962: Insufficient policy enforcement in DirectSockets.
• [497250399] CVE-2026-7963: Inappropriate implementation in ServiceWorker.
• [497254383] CVE-2026-7964: Insufficient validation of untrusted input in FileSystem.
• [497255035] CVE-2026-7965: Insufficient validation of untrusted input in DevTools.
• [497341787] CVE-2026-7966: Insufficient validation of untrusted input in SiteIsolation.
• [497365545] CVE-2026-7967: Insufficient validation of untrusted input in Navigation.
• [497432281] CVE-2026-7968: Insufficient validation of untrusted input in CORS.
• [497450574] CVE-2026-7969: Integer overflow in Network.
• [497487462] CVE-2026-7970: Use after free in TopChrome.
• [497529290] CVE-2026-7971: Inappropriate implementation in ORB.
• [497546281] CVE-2026-7972: Uninitialized Use in GPU.
• [497565944] CVE-2026-7973: Integer overflow in Dawn.
• [497649372] CVE-2026-7974: Use after free in Blink.
• [497735587] CVE-2026-7975: Use after free in DevTools.
• [497736679] CVE-2026-7976: Use after free in Views.
• [497821223] CVE-2026-7977: Inappropriate implementation in Canvas.
• [497828892] CVE-2026-7978: Inappropriate implementation in Companion.
• [497849876] CVE-2026-7979: Inappropriate implementation in Media.
• [497859275] CVE-2026-7980: Use after free in WebAudio.
• [497926602] CVE-2026-7981: Out of bounds read in Codecs.
• [497952533] CVE-2026-7982: Uninitialized Use in WebCodecs.
• [497975608] CVE-2026-7983: Out of bounds read in Dawn.
• [498277368] CVE-2026-7984: Use after free in ReadingMode.
• [498352423] CVE-2026-7985: Use after free in GPU.
• [498396238] CVE-2026-7986: Insufficient policy enforcement in Autofill.
• [498696266] CVE-2026-7987: Use after free in WebRTC.
• [498753456] CVE-2026-7988: Type Confusion in WebRTC.
• [498765082] CVE-2026-7989: Insufficient data validation in DataTransfer.
• [498892267] CVE-2026-7990: Insufficient validation of untrusted input in Updater.
• [499065126] CVE-2026-7991: Use after free in UI.
• [499067529] CVE-2026-7992: Insufficient validation of untrusted input in UI.
• [499099003] CVE-2026-7993: Insufficient validation of untrusted input in Payments.
• [499116954] CVE-2026-7994: Inappropriate implementation in Chromoting.
• [501745798] CVE-2026-7995: Out of bounds read in AdFilter.

Low:

• [484547631] CVE-2026-7996: Insufficient validation of untrusted input in SSL.
• [487960705] CVE-2026-7997: Insufficient validation of untrusted input in Updater.
• [491676472] CVE-2026-7998: Insufficient validation of untrusted input in Dialog.
• [493099941] CVE-2026-7999: Inappropriate implementation in V8.
• [494464734] CVE-2026-8000: Insufficient validation of untrusted input in ChromeDriver.
• [494764371] CVE-2026-8001: Use after free in Printing.
• [495779613] CVE-2026-8002: Use after free in Audio.
• [495985532] CVE-2026-8003: Insufficient validation of untrusted input in TabGroups.
• [496189510] CVE-2026-8004: Insufficient policy enforcement in DevTools.
• [496298665] CVE-2026-8005: Insufficient validation of untrusted input in Cast.
• [496373088] CVE-2026-8006: Insufficient policy enforcement in DevTools.
• [496399759] CVE-2026-8007: Insufficient validation of untrusted input in Cast.
• [496426191] CVE-2026-8008: Inappropriate implementation in DevTools.
• [496555077] CVE-2026-8009: Inappropriate implementation in Cast.
• [496624084] CVE-2026-8010: Insufficient validation of untrusted input in SiteIsolation.
• [496626029] CVE-2026-8011: Insufficient policy enforcement in Search.
• [496628298] CVE-2026-8012: Inappropriate implementation in MHTML.
• [497427430] CVE-2026-8013: Insufficient validation of untrusted input in FedCM.
• [497490364] CVE-2026-8014: Inappropriate implementation in Preload.
• [497548558] CVE-2026-8015: Inappropriate implementation in Media.
• [497695401] CVE-2026-8016: Use after free in WebRTC.
• [497722578] CVE-2026-8017: Side-channel information leakage in Media.
• [498292657] CVE-2026-8018: Insufficient policy enforcement in DevTools.
• [498353173] CVE-2026-8019: Insufficient policy enforcement in WebApp.
• [498382925] CVE-2026-8020: Uninitialized Use in GPU.
• [498417031] CVE-2026-8021: Script injection in UI.
• [499194407] CVE-2026-8022: Inappropriate implementation in MHTML.

https://jira.mongodb.org/browse/SERVER-119981 reports:

• Computing the MD5 checksum of a malformed BSON object under specific conditions may cause loss of availability in MongoDB server.
• An authorization flaw in the user management command could allow an authenticated user to make limited changes to authentication-related data associated with another user account. This could affect how authentication is performed for the impacted account.

https://github.com/ocaml/opam/releases/tag/2.5.1 reports:

In OCaml opam before 2.5.1, a .install field containing a destination filepath can use ../ to reach a parent directory.

Reported by Andrew Nesbitt <andrewnez@gmail.com>.

The Apache httpd project reports:

mod_proxy_ajp: CVE-2026-34059, CVE-2026-34032, CVE-2026-33857, CVE-2026-28780

multiple modules: CVE-2026-33523

mod_authn_socache: CVE-2026-33007

mod_auth_digest: CVE-2026-33006

mod_dav_lock: mod_dav_lock

mod_md: CVE-2026-29168

mod_rewrite: CVE-2026-24072

mod_http2: CVE-2026-23918

ModSecurity is an open source web application firewall engine.

According to the upstream changelog, multiple vulnerabilities have been fixed.

• CVE-2026-42268: unsigned integer underflow in verify operators
• CVE-2026-30923: buffer overflow in hex_decode

https://bugzilla.mozilla.org/buglist.cgi?bug_id=2028537%2C2029911%2C2031121%2C2033602 reports:

Memory safety bugs. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

The Prosody team reports:

Traffic patterns were discovered which can cause Prosody to consume excessive amounts of memory with much smaller amounts of incoming traffic. This traffic can be sent by unauthenticated connections. It was discovered that mod_proxy65’s access control was broken and incomplete due to two bugs.

The issue with unpausing connections was discovered and disclosed by Max Hearnden.

H.Merijn Brand - Tux <linux@tux.freedom.nl> reports:

Text::CSV_XS versions before 1.62 for Perl have a use-after-free when registered callbacks extend the Perl argument stack, which may enable type confusion or memory corruption. The Parse, print, getline, and getline_all methods invoke registered callbacks (for example after_parse, before_print, or on_error) and cache the Perl argument stack pointer across the call. If a callback extends the argument stack enough to trigger a reallocation, the return value is written through the stale pointer into the freed buffer, and the caller reads the original $self argument as the return value instead. Calling code that expects parsed data from getline_all receives the Text::CSV_XS object in its place, leading to logic errors or crashes. Text::CSV_XS objects used without any registered callbacks are not affected.

Problem Description:

When processing the header of an incoming message, libnv failed to properly validate the message size.

Impact:

The lack of validation allows a malicious program to write outside the bounds of a heap allocation. This can trigger a crash or system panic, and it may be possible for an unprivileged user to exploit the bug to elevate their privileges.

Problem Description:

When exchanging data over a socket, libnv uses select(2) to wait for data to arrive. However, it does not verify whether the provided socket descriptor fits in select(2)'s file descriptor set size limit of FD_SETSIZE (1024).

Impact:

An attacker who is able to force a libnv application to allocate large file descriptors, e.g., by opening many descriptors and executing a program which is not careful to close them upon startup, can trigger stack corruption. If the target application is setuid-root, then this could be used to elevate local privileges.

Problem Description:

As dhclient is building an environment to pass to dhclient-script, it may need to resize the array of string pointers. The code which expands the array incorrectly calculates its new size when requesting memory, resulting in a heap buffer overrun.

Impact:

A specially crafted packet can cause dhclient to overrun its buffer of environment entries. This can result in a crash, but it may be possible to leverage this bug to achieve remote code execution.

Problem Description:

Incorrect packet validation allowed unbounded recursion parsing SCTP chunk parameters. This can eventually result in a stack overflow and panic.

Impact:

Remote attackers can craft packets which cause affected systems to panic. This affects any system where pf is configured to process traffic, independent of the configured ruleset.

Problem Description:

An operator precedence bug in the kernel results in a scenario where a buffer overflow causes attacker-controlled data to overwrite adjacent execve(2) argument buffers.

Impact:

The bug may be exploitable by an unprivileged user to obtain superuser privileges.

Problem Description:

The BOOTP file field is written to the lease file without escaping embedded double-quotes, allowing injection of arbitrary dhclient.conf directives. When the lease file is subsequently re-parsed by dhclient, e.g., after a system restart, an attacker-controlled field from the lease is passed to dhclient-script(8), which evaluates it.

Impact:

A rogue DHCP server may be able to execute arbirary code as root on a system running dhclient.

Cary Phillips reports:

[OpenEXR v3.4.11 is a p]atch release that addresses the following security vulnerabilities:

• CVE-2026-42217 Shift exponent overflow in readVariableLengthInteger() (ImfIDManifest.cpp)
• CVE-2026-42216 Out-of-bounds read in IDManifest::init() during prefix expansion
• CVE-2026-41142 Integer overflow in ImageChannel::resize leads to heap OOB write via OpenEXRUtil public API
• OSS-fuzz 504280155 Heap-buffer-overflow in DwaCompressor_uncompress
• OSS-fuzz 505062709 Null-dereference READ in Imf_3_3::prefixFromLayerName

https://bugzilla.mozilla.org/show_bug.cgi?id=2029461 reports:

Sandbox escape due to incorrect boundary conditions in the WebRTC: Networking component.

https://bugzilla.mozilla.org/buglist.cgi?bug_id=2021904%2C2022731%2C2027158%2C2027733%2C2027973%2C2027976%2C2028231%2C2028731%2C2028886%2C2029067%2C2029700%2C2029724%2C2029806%2C2029814%2C2030108%2C2030111%2C2031524%2C2031921%2C2032040 reports:

Memory safety bugs. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

https://bugzilla.mozilla.org/show_bug.cgi?id=2027433 reports:

Information disclosure due to incorrect boundary conditions in the Audio/Video component.

https://bugzilla.mozilla.org/buglist.cgi?bug_id=2029419%2C2029717%2C2029769%2C2029886 reports:

Memory safety bugs. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

https://bugzilla.mozilla.org/show_bug.cgi?id=2027433 reports:

Information disclosure due to incorrect boundary conditions in the Audio/Video component.

https://bugzilla.mozilla.org/buglist.cgi?bug_id=2010727%2C2019004%2C2019224%2C2019547%2C2020378%2C2022381%2C2022608%2C2022785%2C2023120%2C2023128%2C2023140%2C2023279%2C2023836%2C2023882%2C2023925%2C2023950%2C2023959%2C2023965%2C2024243%2C2024245%2C2024247%2C2024253%2C2024346%2C2024357%2C2024416%2C2024420%2C2024429%2C2024432%2C2024455%2C2024466%2C2024468%2C2024476%2C2024664%2C2024666%2C2024669%2C2024670%2C2024671%2C2024761%2C2024918%2C2025292%2C2025332%2C2025348%2C2025384%2C2025395%2C2025458%2C2025461%2C2025463%2C2025481%2C2025483%2C2025485%2C2025494%2C2025506%2C2025511%2C2025513%2C2025520%2C2026277%2C2026282%2C2026288%2C2026289%2C2026311%2C2026312%2C2026869%2C2027152%2C2027161%2C2027238%2C2027261%2C2027269%2C2027274%2C2027280%2C2027281%2C2027300%2C2027302%2C2027331%2C2027339%2C2027340%2C2027738%2C2027975%2C2028000%2C2028011%2C2028289%2C2028525%2C2028728%2C2028887%2C2028888%2C2028896%2C2029063%2C2029064%2C2029290%2C2029291%2C2029294%2C2029300%2C2029304%2C2029316%2C2029317%2C2029401%2C2029415%2C2029430%2C2029457%2C2029727%2C2029735%2C2029743%2C2029752%2C2029754%2C2029776%2C2029809%2C2030324%2C2030370 reports:

Memory safety bugs present. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

https://bugzilla.mozilla.org/buglist.cgi?bug_id=1935995%2C1999158%2C2015952%2C2021909%2C2022026%2C2022041%2C2022088%2C2022276%2C2022335%2C2022338%2C2022373%2C2022597%2C2022874%2C2023276%2C2023544%2C2023551%2C2023599%2C2023608%2C2023814%2C2024233%2C2024239%2C2024241%2C2024242%2C2024250%2C2024251%2C2024343%2C2024422%2C2024425%2C2024440%2C2024442%2C2024446%2C2024458%2C2024463%2C2024478%2C2024650%2C2024653%2C2024654%2C2024655%2C2024656%2C2024661%2C2024662%2C2024668%2C2024919%2C2025278%2C2025349%2C2025350%2C2025354%2C2025360%2C2025363%2C2025370%2C2025379%2C2025381%2C2025399%2C2025400%2C2025403%2C2025407%2C2025415%2C2025420%2C2025427%2C2025429%2C2025430%2C2025479%2C2025489%2C2025493%2C2025497%2C2025502%2C2025515%2C2025517%2C2025526%2C2025609%2C2025948%2C2025949%2C2025951%2C2025953%2C2025955%2C2025962%2C2025969%2C2025970%2C2025971%2C2025973%2C2025976%2C2025977%2C2026280%2C2026285%2C2026293%2C2026296%2C2026310%2C2027237%2C2027260%2C2027268%2C2027277%2C2027284%2C2027291%2C2027293%2C2027298%2C2027330%2C2027342%2C2027345%2C2027359%2C2027365%2C2027378%2C2027754%2C2027959%2C2027962%2C2027964%2C2027971%2C2027974%2C2027979%2C2027982%2C2027995%2C2028001%2C2028267%2C2028268%2C2028275%2C2028288%2C2028290%2C2028291%2C2028528%2C2028551%2C2028627%2C2028879%2C2028889%2C2029061%2C2029071%2C2029283%2C2029296%2C2029314%2C2029323%2C2029411%2C2029423%2C2029424%2C2029425%2C2029427%2C2029436%2C2029440%2C2029449%2C2029450%2C2029458%2C2029462%2C2029468%2C2029472%2C2029690%2C2029707%2C2029708%2C2029728%2C2029802%2C2029896%2C2029906%2C2030106%2C2030118%2C2030123%2C2030135%2C2030230%2C2030320 reports:

Memory safety bugs. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

https://bugzilla.mozilla.org/buglist.cgi?bug_id=1536243%2C1745382%2C1851073%2C1893400%2C1963301%2C2001319%2C2002899%2C2012436%2C2014435%2C2016901%2C2019916%2C2020486%2C2020612%2C2020817%2C2021788%2C2022051%2C2022367%2C2022431%2C2023302%2C2023670%2C2024225%2C2024238%2C2024240%2C2024265%2C2024367%2C2024369%2C2024424%2C2024760%2C2025281%2C2025361%2C2025387%2C2025466%2C2025954%2C2025958%2C2026278%2C2026292%2C2026297%2C2026378%2C2027148%2C2027287%2C2027341%2C2027384%2C2027427%2C2027694%2C2027993%2C2028009%2C2028270%2C2028416%2C2028524%2C2029295%2C2029301%2C2029461%2C2029699%2C2029800%2C2029801 reports:

Memory safety bugs. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.

https://bugzilla.mozilla.org/show_bug.cgi?id=2027564 reports:

Incorrect boundary conditions, integer overflow in the Audio/Video: Playback component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2026571 reports:

Information disclosure in the IP Protection component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2025583 reports:

Denial-of-service in the Audio/Video: Playback component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2023343 reports:

Other issue in the JavaScript Engine component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2022746 reports:

Invalid pointer in the Audio/Video: Playback component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2022726 reports:

Other issue in the Networking: DNS component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2021770 reports:

Incorrect boundary conditions in the WebRTC: Networking component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2021768 reports:

Incorrect boundary conditions in the WebRTC component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2016915 reports:

Mitigation bypass in the DOM: Security component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2015959 reports:

Denial-of-service due to integer overflow in the Graphics: WebGPU component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2026089 reports:

Incorrect boundary conditions in the Libraries component in NSS.

https://bugzilla.mozilla.org/show_bug.cgi?id=2025067 reports:

Mitigation bypass in the DOM: Security component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2024220 reports:

Other issue in the Storage: IndexedDB component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2023753 reports:

Privilege escalation in the Debugger component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2023615 reports:

Mitigation bypass in the Networking: Cookies component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2023209 reports:

Other issue in the Libraries component in NSS.

https://bugzilla.mozilla.org/show_bug.cgi?id=2023207 reports:

Incorrect boundary conditions in the Libraries component in NSS.

https://bugzilla.mozilla.org/show_bug.cgi?id=2022419 reports:

Information disclosure in the Form Autofill component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2022162 reports:

Incorrect boundary conditions in the DOM: Device Interfaces component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2021666 reports:

Mitigation bypass in the File Handling component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2021080 reports:

Spoofing issue in the DOM: Core & HTML component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2017857 reports:

Privilege escalation in the Networking component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2016923 reports:

Mitigation bypass in the Networking: Cookies component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2016164 reports:

Use-after-free in the Widget: Cocoa component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2013619 reports:

Use-after-free in the JavaScript: WebAssembly component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2013588 reports:

Invalid pointer in the JavaScript: WebAssembly component.

https://bugzilla.mozilla.org/show_bug.cgi?id=1880429 reports:

Mitigation bypass in the DOM: postMessage component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2027541 reports:

Use-after-free in the JavaScript Engine component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2027501 reports:

Incorrect boundary conditions in the WebRTC component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2027499 reports:

Incorrect boundary conditions in the WebRTC component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2025883 reports:

Uninitialized memory in the Audio/Video: Web Codecs component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2023407 reports:

Privilege escalation in the Graphics: WebRender component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2022610 reports:

Information disclosure due to uninitialized memory in the Graphics: Canvas2D component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2022604 reports:

Uninitialized memory in the Audio/Video: Web Codecs component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2021769 reports:

Use-after-free in the WebRTC component.

https://bugzilla.mozilla.org/show_bug.cgi?id=2014596 reports:

Use-after-free in the DOM: Core & HTML component.

The X.Org project reports:

libXpm uses a number of internal helper functions to parse the XPM file format. One of these internal functions, xpmNextString(), checks for the NULL terminator when looking for the end of the current string but not when looking for the beginning of the next string. A small XPM file with a malformed color table definition may cause the function xpmNextWord(), called from xpmParseColors() following a call to xpmNextString(), to start past the actual end of the file, causing an out-of-bound read.

https://github.com/libexpat/libexpat/pull/1183 reports:

libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.

https://github.com/mm2/Little-CMS/commit/da6110b1d14abc394633a388209abd5ebedd7ab0 reports:

Little CMS (lcms2) through 2.18 has an integer overflow in CubeSize in cmslut.c because the overflow check is performed after the multiplication.