https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T19:41:04.174163+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2023-06208 bdu:2023-06208 2026-10-02T19:41:04.392681+00:00 bdu:2023-06208 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1103 certfr-2024-avi-1103 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan… 2026-10-02T19:41:04.392725+00:00 certfr-2024-avi-1103 https://cve.radiocsirt.org/vuln/euvd-2026-7351 EUVD-2026-7351 2026-10-02T19:41:04.392747+00:00 EUVD-2026-7351 https://cve.radiocsirt.org/vuln/fkie_cve-2023-4759 fkie_cve-2023-4759 2026-10-02T19:41:04.392760+00:00

Arbitrary File Overwrite in Eclipse JGit <= 6.6.0

In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem.

This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command.

The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration.

Setting git configuration option core.symlinks = false before checking out avoids the problem.

The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ . A backport is available in 5.13.3 starting from 5.13.3.202401111512-r.

The JGit maintainers would like…

 https://cve.radiocsirt.org/vuln/ghsa-3p86-9955-h393 GHSA-3p86-9955-h393 — Arbitrary File Overwrite in Eclipse JGit 2026-10-02T19:41:04.392807+00:00

Affected: Maven: org.eclipse.jgit:org.eclipse.jgit

Arbitrary File Overwrite in Eclipse JGit <= 6.6.0

In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem.

This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command.

The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration.

Setting git configuration option core.symlinks = false before checking out avoids the problem.

The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ . A backport is available in 5.13.3 starting from 5.13.3.202401111512-r.

The JGit maintainers would like to…

 https://cve.radiocsirt.org/vuln/gsd-2023-4759 gsd-2023-4759 2026-10-02T19:41:04.392847+00:00 gsd-2023-4759 https://cve.radiocsirt.org/vuln/oesa-2023-1995 OESA-2023-1995 — jgit security update 2026-10-02T19:41:04.392860+00:00

Affected: openEuler:20.03-LTS-SP1: jgit, openEuler:20.03-LTS-SP3: jgit, openEuler:20.03-LTS-SP4: jgit, openEuler:22.03-LTS: jgit, openEuler:22.03-LTS-SP1: jgit, openEuler:22.03-LTS-SP2: jgit

A pure Java implementation of the Git version control system and command line interface. Security Fix(es): Arbitrary File Overwrite in Eclipse JGit &lt;= 6.6.0 In Eclipse JGit, all versions &lt;= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem. This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command. The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration. Setting git configuration option core.symlinks = false before checking out avoids the problem. The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and repo.eclipse.org https://repo.eclipse.org/content/reposit…

 https://cve.radiocsirt.org/vuln/opensuse-su-2024:13312-1 openSUSE-SU-2024:13312-1 — eclipse-jgit-5.11.0-9.1 on GA media 2026-10-02T19:41:04.392902+00:00

eclipse-jgit-5.11.0-9.1 on GA media

 https://cve.radiocsirt.org/vuln/rhsa-2024:0710 RHSA-2024:0710 — Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.15 Security update 2026-10-02T19:41:04.392920+00:00

jgit: arbitrary file overwrite santuario: Private Key disclosure in debug-log output

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-4759 UBUNTU-CVE-2023-4759 2026-10-02T19:41:04.392938+00:00

Affected: Ubuntu:16.04:LTS: jgit, Ubuntu:18.04:LTS: jgit, Ubuntu:20.04:LTS: jgit, Ubuntu:22.04:LTS: jgit, Ubuntu:24.04:LTS: jgit, Ubuntu:25.10: jgit, Ubuntu:26.04:LTS: jgit

Arbitrary File Overwrite in Eclipse JGit <= 6.6.0 In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem. This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command. The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration. Setting git configuration option core.symlinks = false before checking out avoids the problem. The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/  and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ . A backport is available in 5.13.3 starting from 5.13.3.202401111512-r. The JGit maintainers would like to than…

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0311 WID-SEC-W-2024-0311 — Red Hat JBoss A-MQ: Mehrere Schwachstellen 2026-10-02T19:41:04.392977+00:00

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat JBoss A-MQ und Red Hat Enterprise Linux ausnutzen, um Informationen offenzulegen oder beliebigen Programmcode auszuführen.