https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-29T09:27:14.895151+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-1229 CVE-2026-1229 — Incorrect calculation in CIRCL secp384r1 CombinedMult 2026-09-29T09:27:14.919370+00:00

Affected: Cloudflare CIRCL

The CombinedMult function in the CIRCL ecc/p384 package (secp384r1 curve) produces an incorrect value for specific inputs. The issue is fixed by using complete addition formulas. ECDH and ECDSA signing relying on this curve are not affected.

The bug was fixed in v1.6.3 https://github.com/cloudflare/circl/releases/tag/v1.6.3 .

 https://vulnerability.circl.lu/vuln/ghsa-crhj-59gh-8x96 GHSA-crhj-59gh-8x96 — go-git: Crafted repositories may modify main and submodule .git directories 2026-09-29T09:27:14.919512+00:00

Affected: Go: github.com/go-git/go-git/v5, Go: github.com/go-git/go-git/v6, Go: github.com/go-git/go-git

### Impact A path validation issue in `go-git` could allow crafted repository data to affect files outside the intended checkout target, including the repository's `.git` directory.

These validations were introduced in upstream Git years ago, so the vulnerability arose from go-git drifting from those checks. Some attack vectors were platform-specific: certain payloads affected only Windows users, others affected only macOS users, and some applied across all supported platforms.

Using non-descendant `go-billy` filesystem instances, or different filesystem types, for the `Storer` and `Worktree` may provide some isolation against `.git` directory manipulation. For example, users that store the `.git` directory through `memfs` while using `osfs` for the worktree are not affected by this vulnerability in the main repository, because repository metadata is not materialized inside the worktree filesystem.

However, this isolation does not necessarily apply when the repository contains submodules, since submodule dotgit directories may still be represented or materialized within the worktree context.

It is important to note that exploitation requires a maliciously crafted repository payload. Users should always exercise caution when interacting with repositories or Git servers they do not trust.

### Patches Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to `v5` are likely to be affected, users are recommended to upgrade to a sup…