CVE-2026-27141

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server.

Security Fix(es):

The filepath.Walk and filepath.WalkDir functions are documented as not following symbolic links, but both functions are susceptible to a TOCTOU (time of check/time of use) race condition where a portion of the path being walked is replaced with a symbolic link while the walk is in progress.(CVE-2024-8244)

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.(CVE-2025-27613)

Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.(CVE-2025-4673)

If the PATH environment variable contains paths which are executables (rather than just directories), passing certain strings to LookPath ("", ".", and ".."), can result in the binaries listed in the PATH being unexpectedly returned.(CVE-2025-47906)

When using http.CrossOriginProtection, the AddInsecureBypassPattern method can unexpectedly bypass more requests than intended. CrossOriginProtection then skips validation, but forwards the original request path, which may be served by a different handler without the intended security protections.(CVE-2025-47910)

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.(CVE-2025-47912)

SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.(CVE-2025-47914)

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.(CVE-2025-48385)

SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.(CVE-2025-58181)

A vulnerability was found in Google Go up to 1.25.1 (Programming Language Software). It has been rated as…

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server.

Security Fix(es):

Processing an incomplete post-handshake message for a QUIC connection can cause a panic.(CVE-2023-39321)

QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size.(CVE-2023-39322)

The filepath.Walk and filepath.WalkDir functions are documented as not following symbolic links, but both functions are susceptible to a TOCTOU (time of check/time of use) race condition where a portion of the path being walked is replaced with a symbolic link while the walk is in progress.(CVE-2024-8244)

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.(CVE-2025-22874)

Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.(CVE-2025-26625)

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.(CVE-2025-27613)

Gitk is a Tcl/Tk based Git history browser. Starting with 2.41.0, a Git repository can be crafted in such a way that with some social engineering a user who has cloned the repository can be tricked into running any script (e.g., Bourne shell, Perl, Python, ...) supplied by the attacker by invoking gitk filename, where filename has a particular structure. The script is run with the privileges of the user. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.(CVE-2025-27614)

Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.(CVE-2025-4673)

The go command may execute unexpected commands when operating in untrusted VCS repositories. This occurs when possibly dangerous VCS configuration is present in repositories. This can happen when a repository was fetched via one VCS (e.g. Git), but contains metadata for another VCS (e.g. Mercurial). Modules which are retrieved using the go command line,…

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

This update bring new features, bugs and vulnerabilities fixed in rclone and golang components used to build it.

These are all security issues fixed in the telemetrygen-0.147.0-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the rclone-1.73.2-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the traefik-3.6.10-2.1 package on the GA media of openSUSE Tumbleweed.

This update for rclone fixes the following issues:

Changes in rclone:

• Update to version 1.73.5:

  • Version v1.73.5
  • operations: add AuthRequired to operations/fsinfo to prevent backend creation CVE-2026-41179
  • rc: snapshot NoAuth at startup to prevent runtime auth bypass CVE-2026-41176
  • rc: add AuthRequired to options/set to prevent auth bypass CVE-2026-41176
  • s3: fix empty delimiter parameter rejected by Archiware P5 server
  • azureblob/auth: add Microsoft Partner Network User-Agent prefix
  • drime: fix User.EntryPermissions JSON unmarshalling
  • filter: fix debug logs that fire before logger is configured - fixes #9291
  • s3: fix TencentCOS CDN endpoint failing on bucket check
  • iclouddrive: fix 'directory not found' error when the directory contains accent marks
  • Start v1.73.5-DEV development

• Update to version 1.73.4:

  • Version v1.73.4
  • Update to go 1.25.9 to fix multiple CVEs
  • build: fix Denial of Service due to Panic in AWS SDK for Go v2 SDK EventStream Decoder
  • docs: fix markdown issues in mount docs
  • docs: fix header level for metadata option
  • fix(docs): Fix link to not be language specific
  • filen: update SDK version
  • build(deps): bump golang.org/x/image from 0.36.0 to 0.38.0
  • docs: note macOS 10.15 (Catalina) support with version v1.70.3
  • Start v1.73.4-DEV development

• Update to version 1.73.3: (CVE-2026-33186 GHSA-6g7g-w4f8-9c9x)

  • Version v1.73.3
  • build(deps): bump github.com/buger/jsonparser from 1.1.1 to 1.1.2
  • docs/jottacloud: fix broken link
  • docs: clarify Filen password change requires updating both password and API key in rclone config
  • docs: note that Filen API key changes on password change
  • build(deps): bump google.golang.org/grpc from 1.79.1 to 1.79.3
  • s3: add multi tenant support for Cubbit
  • lib/rest: fix URLPathEscapeAll breaking WebDAV servers (eg nzbdav) with strict path matching
  • list: fix nil pointer panic in Sorter when temp file creation fails
  • docs: update RELEASE procedure to avoid mistakes
  • docs: added text to the label showing version-introduced info
  • Start v1.73.3-DEV development
  • docs: update sponsors

• Update to version 1.73.2:

  • Version v1.73.2
  • Update to go 1.25.8 to fix multiple CVEs
  • build: update to golang.org/x/net v0.51.0 to fix CVE-2026-27141 #9220
  • docs: fix new drive flag typo in changelog
  • webdav: add missing headers for CORS
  • docs: Document unsupported S3 object keys with double slashes
  • docs: note that --use-server-modtime only works on some backends
  • internxt: fix Entry doesn't belong in directory errors on windows
  • drime: fix chunk-uploaded files ignoring workspace ID
  • docs: Fix headers hierarchy for mount.md
  • webdav: escape reserved characters in URL path segments
  • bisync: add group Sync to the bisync command
  • archive: extract: strip "./" prefix from tar entry paths
  • docs: add instructions on how to update Go version
  • buid: update github.com/cloudflare/circl to v1.6.3 to fix CVE-2026-1229
  • Start v1.73.2-DEV development

• Update to version 1.73.1:

  • Version v1.73.1
  • build: fix build using go 1.26.0 instead of go 1.25.7
  • fs/march: fix runtime: program exceeds 10000-thread limit
  • accounting: fix missing server side stats from core/stats rc
  • pacer: re-read the sleep time as it may be stale
  • pacer: fix deadlock between pacer token and --max-connections
  • build: fix CVE-2025-68121 by updating go to 1.25.7 or later - fixes #9167
  • drime: fix files and directories being created in the default workspace
  • docs: update sponsors
  • copyurl: Extend copyurl docs with an example of CSV FILENAMEs starting with a path.
  • internxt: implement re-login under refresh logic, improve retry logic - fixes #9174
  • docs: add ExchangeRate-API as a sponsor
  • build: bump github.com/go-chi/chi/v5 from 5.2.3 to 5.2.5 to fix GO-2026-4316
  • Set list_version to 2 for FileLu S3 configuration
  • filelu: add multipart upload support…

This update for rclone fixes the following issues:

Changes in rclone:

• Update to version 1.74.4 (boo#1267192):

  • Version v1.74.4
  • gui: update embedded release to 1.1.10
  • local: stop --links symlinks escaping the destination directory CVE-2026-54572
  • local: don't restore setuid/setgid/sticky bits from metadata by default GHSA-945v-v9p3-v5xw
  • s3: strip STS security token on same-host HTTPS->HTTP redirect GHSA-cf44-9pgv-m4xc
  • serve restic: fix --private-repos isolation bypass CVE-2026-59733
  • archive extract: fix path traversal letting archives escape the destination CVE-2026-59732
  • serve s3: fix path traversal letting clients see files in the root GHSA-8v25-v8p6-qf7v
  • build: fix multiple CVEs by upgrading to go1.26.5
  • s3: fix mounting a prefix failing with 403 when HEAD is not permitted
  • drive, googlephotos: warn when using rclone's shared client_id #9580
  • drive: fix stray %!(EXTRA) in unexportable google document log message
  • serve/http: fix --disable-zip so it works over rc
  • serve webdav: fix MOVE overwrite failing without Overwrite header
  • fs: fix negative offset when a suffix Range request exceeds object size
  • accounting: fix goroutine leak in NewStatsGroup for zero-transfer rc jobs
  • cmd/mount2: fix NFS directory listings by supporting non-zero Seekdir offsets
  • cmd/mount2: fix ESTALE over NFS by reporting stable inode numbers
  • cmd/mount2: fix NFS file creation by implementing Mknod
  • smb: fix for IBM iSeries and signature verification
  • mega: fix hard deleted files reappearing in listings - fixes #9554
  • mega: wait for server events after upload, delete and move
  • vfs: fix hang reopening a file during the handle-caching grace period
  • s3: correct documented copy_cutoff minimum to 1 byte - Fixes #7391
  • fs: fix command line flag being ignored when set to its default value
  • docs: fix copy to clipboard functionality for code blocks
  • fs/operations: correct DeleteFile --backup-dir documentation
  • build: update golang.org/x/image to v0.43.0 to fix image decoding vulnerabilities
  • docs: clarify copyto command description - Fixes #9527
  • docs: fix typo in remote setup docs
  • serve s3: fix spurious 404 on HEAD/GET during VFS writeback - fixes #8188
  • • s3: fix error mapping in GetObject to match HeadObject
  • filter: fix --files-from copy stopping at the first unreadable file
  • docs: Fix RELEASE.md
  • ncdu: fix duplicated keystrokes on Windows by pinning tcell to v2.9.0
  • completion: fix powershell completion corrupting non-ASCII names - fixes #9412
  • docs/crypt: fix encrypted size example - Fixes #9202
  • docs: drive: note Google verification exemption for personal use apps
  • rc: document that rc API access is equivalent to shell access
  • docs: drive: update documentation about "Computers" folder
  • accounting: fix goroutine leak in ResetCounters
  • docs: fix --windows-event-log-level help
  • backend/filelu: fix recursive listing path handling and file filtering
  • docs: bisync - clarify flag interaction and minor changes
  • docs: Update RELEASE.md to use cherry-pick -x
  • webdav: fix mixed property statuses in multi-status responses
  • s3: remove session token on cross-host redirects
  • drive: warn when non-exportable Google documents are skipped - #9475
  • Start v1.74.4-DEV development

• update x/image to 0.43 (bsc#1271056)

• Update to version 1.74.3: (boo#1267869)

  • Bug Fixes
    • rc
      • Fix unauthenticated command execution via --rc-serve inline remotes CVE-2026-49980 (Nick Craig-Wood)
      • Stop global.* connection string options changing config CVE-2026-49980 (Nick Craig-Wood)
    • build: Fix multiple CVEs by upgrading to go1.26.4 (Nick Craig-Wood)
      • CVE-2026-42504: mime: quadratic complexity in WordDecoder.DecodeHeader
      • CVE-2026-42507: net/textproto: arbitrary input are included in errors without any escaping
      • CVE-2026-27145: crypto/x509: split…

This update for govulncheck-vulndb fixes the following issues:

• Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

• GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
• GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
• GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
• GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
• GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
• GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
• GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
• GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
• GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
• GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
• GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
• GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
• GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
• GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
• GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
• GO-2026-5933 GHSA-3g4q-2f67-2gvh
• GO-2026-5934 GHSA-59qp-cfj3-rp64
• GO-2026-5935 GHSA-7856-g3gv-9wq8
• GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
• GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
• GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
• GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
• GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
• GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
• GO-2026-5942 CVE-2026-46600
• GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
• GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
• GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
• GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
• GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
• GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
• GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
• GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
• GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
• GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
• GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
• GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
• GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
• GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
• GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
• GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
• GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
• GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
• GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
• GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
• GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
• GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
• GO-2026-5969 GHSA-g936-7jqj-mwv8
• GO-2026-5970 CVE-2026-56852
• GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
• GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
• GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
• GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
• GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
• GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
• GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
• GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
• GO-2026-5981 GHSA-mqxv-9rm6-w8qc
• GO-2026-5982 GHSA-pqg7-v6wh-3pfp
• GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
• GO-2026-5985 GHSA-7rx3-5wx3-5v76
• GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
• GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
• GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
• GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
• GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
• GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
• GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
• GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
• GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
• GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
• GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
• GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
• GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
• GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
• GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
• GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…

This update for govulncheck-vulndb fixes the following issues:

Update to version 0.0.20260226T182644 2026-02-26T18:26:44Z (jsc#PED-11136) Go CVE Numbering Authority IDs added or updated with aliases:

• GO-2025-4259 CVE-2025-13767 GHSA-fmqf-pmcm-8cx9
• GO-2025-4260 CVE-2025-64641 GHSA-vww6-79rv-3j4x
• GO-2026-4282 CVE-2017-18873 GHSA-x6mw-hf2j-vqpc
• GO-2026-4305 CVE-2017-18903 GHSA-fcwg-45jh-5qhf
• GO-2026-4325 CVE-2025-14822 GHSA-9r42-rhw3-2222
• GO-2026-4326 CVE-2025-14435 GHSA-mx8m-v8qm-xwr8
• GO-2026-4332 CVE-2026-23644 GHSA-2657-3c98-63jq
• GO-2026-4348 CVE-2026-23991 GHSA-846p-jg2w-w324
• GO-2026-4349 CVE-2026-23992 GHSA-fphv-w9fq-2525
• GO-2026-4377 CVE-2026-24686 GHSA-jqc5-w2xx-5vq4
• GO-2026-4410 CVE-2026-25140 GHSA-f4w5-5xv9-85f6
• GO-2026-4502 CVE-2026-25766 GHSA-pgvm-wxw2-hrv9
• GO-2026-4534 CVE-2026-25899 GHSA-2mr3-m5q5-wgp6
• GO-2026-4535 CVE-2026-27585 GHSA-4xrr-hq4w-6vf4
• GO-2026-4536 CVE-2026-27590 GHSA-5r3v-vc8m-m96g
• GO-2026-4537 CVE-2026-27589 GHSA-879p-475x-rqh2
• GO-2026-4538 CVE-2026-27587 GHSA-g7pc-pc7g-h8jh
• GO-2026-4539 CVE-2026-27586 GHSA-hffm-g8v7-wrv7
• GO-2026-4540 CVE-2026-25891 GHSA-m3c2-496v-cw3v
• GO-2026-4541 CVE-2026-27588 GHSA-x76f-jf84-rqj8
• GO-2026-4543 CVE-2026-25882 GHSA-mrq8-rjmw-wpq3
• GO-2026-4559 CVE-2026-27141

Update to version 0.0.20260225T230704 2026-02-25T23:07:04Z.

• GO-2026-4358 CVE-2026-24137 GHSA-fcv2-xgw5-pqxf
• GO-2026-4361 GHSA-c32p-wcqj-j677
• GO-2026-4394 CVE-2026-24051 GHSA-9h8m-3fm2-qjrq
• GO-2026-4399 CVE-2026-25518 GHSA-gx3x-vq4p-mhhv
• GO-2026-4507 CVE-2026-26314 GHSA-2gjw-fg97-vg3r
• GO-2026-4508 CVE-2026-26313 GHSA-689v-6xwf-5jf3
• GO-2026-4509 CVE-2026-27017 GHSA-7m29-f4hw-g2vx
• GO-2026-4511 CVE-2026-26315 GHSA-m6j8-rg6r-7mv8
• GO-2026-4512 CVE-2026-26995 GHSA-rrxv-pmq9-x67r
• GO-2026-4531 CVE-2026-25591 GHSA-w6x6-9fp7-fqm4
• GO-2026-4532 CVE-2026-25802 GHSA-299v-8pq9-5gjq
• GO-2026-4533 CVE-2026-27571 GHSA-qrvq-68c2-7grw
• GO-2026-4542 CVE-2026-27598 GHSA-6v48-fcq6-ff23
• GO-2026-4545 CVE-2025-50180 GHSA-3c9r-837r-qqm4
• GO-2026-4546 CVE-2026-27611 GHSA-8vrh-3pm2-v4v6
• GO-2026-4547 CVE-2026-27626 GHSA-49gm-hh7w-wfvf
• GO-2026-4548 GHSA-2phg-qgmm-r638

Update to version 0.0.20260223T182315 2026-02-23T18:23:15Z.

• GO-2026-4392 CVE-2026-24845 GHSA-9m43-p3cx-w8j5
• GO-2026-4434 CVE-2023-43635 GHSA-4jvr-vj2c-8q37
• GO-2026-4435 CVE-2023-43636 GHSA-5h7v-g49c-h887
• GO-2026-4436 CVE-2023-43637 GHSA-g7vp-j25f-h34p
• GO-2026-4442 GHSA-x9p2-77v6-6vhf
• GO-2026-4444 CVE-2026-23989 GHSA-9j2f-3rj3-wgpg
• GO-2026-4445 CVE-2026-25760 GHSA-2286-hxv5-cmp2
• GO-2026-4446 CVE-2026-24851 GHSA-jq9f-gm9w-rwm9
• GO-2026-4447 GHSA-vf5j-r2hw-2hrw
• GO-2026-4448 CVE-2025-64111 GHSA-gg64-xxr9-qhjp
• GO-2026-4449 CVE-2025-64175 GHSA-p6x6-9mx6-26wj
• GO-2026-4450 CVE-2026-23632 GHSA-5qhx-gwfj-6jqr
• GO-2026-4451 CVE-2026-22592 GHSA-cr88-6mqm-4g57
• GO-2026-4452 CVE-2026-24135 GHSA-jp7c-wj6q-3qf2
• GO-2026-4453 CVE-2026-23633 GHSA-mrph-w4hh-gx3g
• GO-2026-4454 GHSA-26gq-grmh-6xm6
• GO-2026-4455 CVE-2025-70963 GHSA-9f8m-9547-2gqm
• GO-2026-4456 CVE-2025-13523 GHSA-ffx7-34p2-vm3w
• GO-2026-4457 CVE-2025-65852 GHSA-rjv5-9px2-fqw6
• GO-2026-4458 CVE-2026-25793 GHSA-69x3-g4r3-p962
• GO-2026-4459 CVE-2017-18907 GHSA-42x9-rr3c-gr59
• GO-2026-4460 CVE-2017-18918 GHSA-5ghq-28r7-qwfj
• GO-2026-4461 CVE-2026-25804 GHSA-86x4-wp9f-wrr9
• GO-2026-4462 CVE-2017-18915 GHSA-hxxj-8phw-74vw
• GO-2026-4463 CVE-2017-18917 GHSA-jxc4-w54c-qv5r
• GO-2026-4464 CVE-2017-18911 GHSA-m462-mqw4-2c8m
• GO-2026-4465 GHSA-vhvq-fv9f-wh4q
• GO-2026-4466 CVE-2026-25791 GHSA-wxrw-gvg8-fqjp
• GO-2026-4467 CVE-2017-18916 GHSA-x33g-375j-jhf7
• GO-2026-4471 CVE-2025-66630 GHSA-68rr-p4fp-j59v
• GO-2026-4473 CVE-2026-25934 GHSA-37cx-329c-33x3
• GO-2026-4474 CVE-2026-25890 GHSA-4mh3-h929-w968
• GO-2026-4475 CVE-2026-25889 GHSA-hxw8-4h9j-hq2r
• GO-2026-4476 CVE-2017-18908…

It was discovered that ADSys did not properly handle certain HTTP/2 frames. A remote attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-27141)

It was discovered that ADSys did not properly handle certain HTTP/2 SETTINGS frames. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-33814)