gnutls: update to 3.8.14.
* Version 3.8.14 (released 2026-11-18)
** libgnutls: Fix crash on certificate list memory allocation failure
On allocation failure, the certificate list pointer and count could
get out of sync, causing a NULL deref or double-free during session cleanup.
Both fields are now zeroized before the allocation.
Reported by Joshua Rogers of AISLE Research Team.
[GNUTLS-SA-2026-11-18-1, severity: low] [CVE-2026-127039]
** libgnutls: Fix crash in RSA-PSK username copy memory allocation failure
A missing return on a failed username copy could crash the handshake
when memory allocation fails.
The error is now propagated, aborting the handshake.
Reported by Joshua Rogers of AISLE Research Team.
[GNUTLS-SA-2026-11-18-2, severity: low] [CVE-2026-127040]
** libgnutls: Make name constraints deinitialization idempotent
[115 lines not shown]
nss: update to 3.134.
Changes:
Bug 2094753 - set bundled NSPR version to 4.41.
Bug 2090488 - Bind server session cache cert slots to their session by cert hash.
Bug 2090403 - Select the write cipher spec per record and keep xmitBufLock during the KeyUpdate key change.
Bug 350261 - softoken should set CKF_WRITE_PROTECTED when NSS is initialized in read-only mode.
Bug 2093682 - Don't call rmdir inside assert in ScopedUniqueDirectory.
Bug 2079584 - ML-KEM certificates can only assert keyEncipherment.
Bug 2093802 - set CKF_USER_PIN_INITIALIZED as appropriate from NSC_GetTokenInfo, not NSC_GetSlotInfo.
Bug 2090359 - Reject Edwards and Montgomery keys whose CKA_EC_PARAMS name another curve.
Bug 2090359 - Validate Ed25519 and X25519 private key lengths and defer caching derived public keys.
Bug 2079584 - support ML-KEM end-entity keys in certutil.
Bug 2090489 - release cached cert references in the callers of transfer_x_certs_to_collection.
Bug 2086988 - Free ephemeral key pairs during SSL_ResetHandshake (TLS).
Bug 2084643 - Add review-context.toml and review guidance for LLM-assisted code review.
Bug 1592984 - Don't fail a password change on attributes with unverifiable MACs.
Bug 2087611 - NSS smime: decode the RC2 capability parameter with QuickDER.
[40 lines not shown]
security/clamav: update to 1.4.7
1.4.7 (2026-11-18)
This is security release.
* CVE-2026-76422: Fixed Rust-to-C logging so rendered messages are passed as
data rather than as C format strings. Crafted input could otherwise cause
a crash, disclose process memory, or corrupt memory when
attacker-controlled text was logged. This issue affects ClamAV 0.105.0
through 1.5.4. The fix is included in 1.4.7 and 1.5.5. Thank you to Feng
Xue for identifying this issue.
* CVE-2026-76411: Fixed URL canonicalization length accounting that could
write beyond a stack buffer while scanning crafted email with full-hash
phishing database entries loaded. This issue affects ClamAV 0.94 through
1.5.4. The fix is included in 1.4.7 and 1.5.5. Thank you to Feng Xue for
identifying this issue.
[65 lines not shown]
security/libmldsa and mldsa: update to version 20261118.
security/mlsignify - new package, providing the same mldsa(1) functionality
but with a command line interface similar to signify(1)
security/libmldsa and mldsa, and new security/mlsignify: update to version 20261118
Changes from previous version:
Bump mldsa to version 20261118
+ add embryonic mlsignify.1 man page
+ spruce up the mldsa.1 man page
+ fixup the Makefile.*.in files
+ specify the other options on the command line for mlsignify(1)
pkgsrc changes:
+ add an mlsignify package, which does the same work as mldsa,
but attempts to use the same command line options as the signify
utility. Note that even though not all signify(1) options make sense
to mlsignify(1), they are recognised, in an attempt to provide
compatibility
kitty: update to 0.51.0
- Allow docking kitty windows to an edge of the OS window, below the
tab bar, with launch --type=os-window-dock. The dock is shown in
every tab of the OS window and can be resized by dragging its inner
border or with the resize_window action and kitten @resize-window,
see Docked windows
- Custom shaders: Add screen-shake shaders that shake a window on
bell and new events and uniforms for command start/finish and
alternate screen enter/exit
- Allow running the programs in new windows via a wrapper command,
such as to open new windows inside the same container as the window
they are opened from, using a launch_wrapper.py file in the kitty
config directory, see Wrapping the programs run in new windows
- Watchers: on_close now reports why the window was closed, a new
on_cwd_change event fires when the working directory changes and
on_resize/on_focus_change calls are no longer dropped when many
windows are created at once
- Tab bar: Allow selecting and copying text drawn outside the tabs,
[67 lines not shown]
fontconfig: update to 2.18.4.
Security fix release.
2.18.4
Akira TAGOH (5):
Guard against mixing plain strings and triples in an FcStrSet
Fix uninitialized read from GNU stderror_r variant
Harden allocation-failure handling flagged by an OpenScanHub audit
Fix crash on odd-addreessed pattern strings
Fix out-of-bounds access in FcCharSetMerge when merging page 0xffff
Dominik Röttsches (3):
Fix arbitrary free in cache validation
Add regression tests for cache value type validation
Validate cache value types against their object
Jeremy Huddleston Sequoia (2):
[9 lines not shown]
nginx: Update to 1.30.7
Changes with nginx 1.30.7 18 Nov 2026
*) Security: a buffer overflow might occur in a worker process when
using the "try_files" and "alias" directives in certain
configurations (CVE-2026-125283).
Thanks to Marc Luchian and Liviu-Alexandru Bud.
*) Security: a flow control window overflow in HTTP/2 might allow an
attacker to cause a segmentation fault in a worker process, or might
have potential other impact (CVE-2026-123007).
Thanks to Xint.io.
*) Security: use-after-free might occur in a worker process when using
HTTP/2 if worker_connections were not enough (CVE-2026-123633).
Thanks to Albert of Vexera AI.
*) Security: use-after-free might occur in a worker process when using
[29 lines not shown]
fixed libssh versions 0.11.2 and up
upstream changed their numbering method and it's not 0.112 but 0.11.2
This will probably not mix well, but at least new vulnerabilities
should not show up as persisting in recent versions that have them fixed