https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T18:26:18.131445+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bit-fluentd-2021-41186 BIT-fluentd-2021-41186 — ReDoS vulnerability in parser_apache2 2026-10-03T18:26:18.139081+00:00

Affected: Bitnami: fluentd

Fluentd collects events from various data sources and writes them to files to help unify logging infrastructure. The parser_apache2 plugin in Fluentd v0.14.14 to v1.14.1 suffers from a regular expression denial of service (ReDoS) vulnerability. A broken apache log with a certain pattern of string can spend too much time in a regular expression, resulting in the potential for a DoS attack. This issue is patched in version 1.14.2 There are two workarounds available. Either don't use parser_apache2 for parsing logs (which cannot guarantee generated by Apache), or put patched version of parser_apache2.rb into /etc/fluent/plugin directory (or any other directories specified by the environment variable `FLUENT_PLUGIN` or `--plugin` option of fluentd).

 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0003 certfr-2025-avi-0003 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan… 2026-10-03T18:26:18.139134+00:00 certfr-2025-avi-0003 https://cve.radiocsirt.org/vuln/euvd-2026-31600 EUVD-2026-31600 2026-10-03T18:26:18.139154+00:00 EUVD-2026-31600 https://cve.radiocsirt.org/vuln/fkie_cve-2021-41186 fkie_cve-2021-41186 2026-10-03T18:26:18.139166+00:00

Fluentd collects events from various data sources and writes them to files to help unify logging infrastructure. The parser_apache2 plugin in Fluentd v0.14.14 to v1.14.1 suffers from a regular expression denial of service (ReDoS) vulnerability. A broken apache log with a certain pattern of string can spend too much time in a regular expression, resulting in the potential for a DoS attack. This issue is patched in version 1.14.2 There are two workarounds available. Either don't use parser_apache2 for parsing logs (which cannot guarantee generated by Apache), or put patched version of parser_apache2.rb into /etc/fluent/plugin directory (or any other directories specified by the environment variable `FLUENT_PLUGIN` or `--plugin` option of fluentd).

 https://cve.radiocsirt.org/vuln/ghsa-hwhf-64mh-r662 GHSA-hwhf-64mh-r662 — ReDoS vulnerability in parser_apache2 2026-10-03T18:26:18.139191+00:00

Affected: RubyGems: fluentd

### Impact parser_apache2 plugin in Fluentd v0.14.14 to v1.14.1 suffers from a regular expression denial of service (ReDoS) vulnerability. A broken apache log with a certain pattern of string can spend too much time in a regular expression, resulting in the potential for a DoS attack.

### Patches v1.14.2

### Workarounds Either of the following:

* Don't use parser_apache2 for parsing logs which cannot guarantee generated by Apache. * Put patched version of parser_apache2.rb into /etc/fluent/plugin directory (or any other directories specified by the environment variable `FLUENT_PLUGIN` or `--plugin` option of fluentd).

### References * [CVE-2021-41186](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41186) * [GHSA-hwhf-64mh-r662](https://github.com/fluent/fluentd/security/advisories/GHSA-hwhf-64mh-r662) * [GHSL-2021-102](https://securitylab.github.com/advisories/GHSL-2021-102-fluent-fluentd/) * https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#v1142

 https://cve.radiocsirt.org/vuln/gsd-2021-41186 gsd-2021-41186 2026-10-03T18:26:18.139236+00:00 gsd-2021-41186 https://cve.radiocsirt.org/vuln/msrc_cve-2021-41186 msrc_CVE-2021-41186 — ReDoS vulnerability in parser_apache2 2026-10-03T18:26:18.139249+00:00 msrc_CVE-2021-41186 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11795-1 openSUSE-SU-2024:11795-1 — ruby3.1-rubygem-fluentd-1.14.4-1.1 on GA media 2026-10-03T18:26:18.139272+00:00

ruby3.1-rubygem-fluentd-1.14.4-1.1 on GA media

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0001 WID-SEC-W-2025-0001 — IBM DB2: Mehrere Schwachstellen 2026-10-03T18:26:18.139287+00:00

Ein entfernter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 on Cloud Pak for Data ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder einen Denial-of-Service-Zustand zu erzeugen.