https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 00:41:14 +0000 https://cve.radiocsirt.org/vuln/bdu:2023-05216 bdu:2023-05216 https://cve.radiocsirt.org/vuln/bdu:2023-05216 https://cve.radiocsirt.org/vuln/bell-cve-2021-26291 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2021-26291 https://cve.radiocsirt.org/vuln/bit-maven-2021-26291 <p><strong>Affected:</strong> Bitnami: maven</p> <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> <p><strong>Affected:</strong> Bitnami: maven</p> <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> https://cve.radiocsirt.org/vuln/bit-maven-2021-26291 https://cve.radiocsirt.org/vuln/certfr-2022-avi-659 certfr-2022-avi-659 https://cve.radiocsirt.org/vuln/certfr-2022-avi-659 https://cve.radiocsirt.org/vuln/cnvd-2021-36229 cnvd-2021-36229 https://cve.radiocsirt.org/vuln/cnvd-2021-36229 https://cve.radiocsirt.org/vuln/euvd-2026-24986 EUVD-2026-24986 https://cve.radiocsirt.org/vuln/euvd-2026-24986 https://cve.radiocsirt.org/vuln/fkie_cve-2021-26291 <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-26291 https://cve.radiocsirt.org/vuln/ghsa-2f88-5hg8-9x2x <p><strong>Affected:</strong> Maven: org.apache.maven:maven-compat, Maven: org.apache.maven:maven-core</p> <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> <p><strong>Affected:</strong> Maven: org.apache.maven:maven-compat, Maven: org.apache.maven:maven-core</p> <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> https://cve.radiocsirt.org/vuln/ghsa-2f88-5hg8-9x2x https://cve.radiocsirt.org/vuln/gsd-2021-26291 gsd-2021-26291 https://cve.radiocsirt.org/vuln/gsd-2021-26291 https://cve.radiocsirt.org/vuln/msrc_cve-2021-26291 msrc_CVE-2021-26291 https://cve.radiocsirt.org/vuln/msrc_cve-2021-26291 https://cve.radiocsirt.org/vuln/oesa-2021-1276 <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: maven, openEuler:20.03-LTS-SP2: maven</p> <p>Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project&amp;apos;s build, reporting and documentation from a central piece of information. Security Fix(es): Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html(CVE-2021-26291)</p> <p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: maven, openEuler:20.03-LTS-SP2: maven</p> <p>Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project&amp;apos;s build, reporting and documentation from a central piece of information. Security Fix(es): Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html(CVE-2021-26291)</p> https://cve.radiocsirt.org/vuln/oesa-2021-1276 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10687-1 <p>clojure-1.10.3.855-1.2 on GA media</p> <p>clojure-1.10.3.855-1.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10687-1 https://cve.radiocsirt.org/vuln/rhsa-2021:3880 <p>jackson-dataformat-cbor: Unchecked allocation of byte buffer can cause a java.lang.OutOfMemoryError exception wildfly-elytron: possible timing attack in ScramServer resteasy: Error message exposes endpoint class information netty: Information disclosure via the local system temporary directory netty: possible request smuggling in HTTP/2 due missing validation netty: Request smuggling via content-length header maven: Block repositories using http by default</p> <p>jackson-dataformat-cbor: Unchecked allocation of byte buffer can cause a java.lang.OutOfMemoryError exception wildfly-elytron: possible timing attack in ScramServer resteasy: Error message exposes endpoint class information netty: Information disclosure via the local system temporary directory netty: possible request smuggling in HTTP/2 due missing validation netty: Request smuggling via content-length header maven: Block repositories using http by default</p> https://cve.radiocsirt.org/vuln/rhsa-2021:3880 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-26291 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: maven, Ubuntu:Pro:16.04:LTS: maven, Ubuntu:Pro:18.04:LTS: maven, Ubuntu:Pro:20.04:LTS: maven, Ubuntu:Pro:22.04:LTS: maven</p> <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: maven, Ubuntu:Pro:16.04:LTS: maven, Ubuntu:Pro:18.04:LTS: maven, Ubuntu:Pro:20.04:LTS: maven, Ubuntu:Pro:22.04:LTS: maven</p> <p>Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-26291 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1375 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in JFrog Artifactory ausnutzen, um seine Privilegien zu erweitern, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen und einen Denial-of-Service-Zustand auszulösen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in JFrog Artifactory ausnutzen, um seine Privilegien zu erweitern, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen und einen Denial-of-Service-Zustand auszulösen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1375