Is rsyslog safe to use?

Vulert records 1 vulnerabilities for rsyslog in Red Hat: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does rsyslog have?

1 vulnerability is recorded for rsyslog in the Red Hat ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rsyslog vulnerabilities disclosed?

1 vulnerability was recorded for rsyslog in the last 12 months, and the oldest entry in this database dates to 20 Oct 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rsyslog are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rsyslog for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the rsyslog version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

Vulnerability Database · Red Hat · Package report

rsyslog: vulnerability history, versions and safety

rsyslog is a package in the Red Hat ecosystem. Vulert records 1 vulnerability for it across 1 affected range, first recorded in Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded U1

0 with no fix published

Every vulnerability has a patched version to move to.

1 in the last 12 months

Most recent disclosure 20 Oct 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rsyslog vulnerabilities

Vulert verdict on rsyslog i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 20 Oct 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 1 vulnerability on record across 1 year, 1 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

Vulnerabilities on record 1 over 1 year · 1 in the last year i
Latest disclosure 20 Oct 2026 i
Highest CVSS 7.5 i
With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

Affected range	Vulnerabilities
up to 0:8.2310.0-4.el9_4.1 (exclusive)	1

02 Disclosure history

How often vulnerabilities are recorded

2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for rsyslog

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Critical Security Flaw in Rsyslog Package: CVE-2026-19654	7.5 high	0:8.2310.0-4.el9_4.1	20 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315