VulertSecurity VulertSecurity

Vulnerability Database · Red Hat · Package report

xmlsec1: vulnerability history, versions and safety

xmlsec1 is a package in the Red Hat ecosystem. Vulert records 2 vulnerabilities for it across 2 affected ranges, first recorded in Sep 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all xmlsec1 vulnerabilities

Vulert verdict on xmlsec1 i

Updated on 22 Oct 2026

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

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 1 year, none 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 2 over 1 year · 0 in the last year i
  • Latest disclosure 15 Sep 2024 i
  • Highest CVSS n/a 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.

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.

i
Affected range Vulnerabilities
up to 0:1.2.6-3.2 (exclusive) 1
up to 0:1.2.6-3.1 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for xmlsec1

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Security Advisory: xmlsec1 Vulnerability in Red Hat Enterprise Linux N/A unrated 0:1.2.6-3.1 13 Sep 2024
Critical Security Update for xmlsec1: Addressing CVE-2011-1425 Vulnerability N/A unrated 0:1.2.6-3.2 15 Sep 2024

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About xmlsec1

Is xmlsec1 safe to use?

Vulert records 2 vulnerabilities for xmlsec1 in Red Hat: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 xmlsec1 have?

2 vulnerabilities are recorded for xmlsec1 in the Red Hat ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 xmlsec1 vulnerabilities disclosed?

0 vulnerabilities were recorded for xmlsec1 in the last 12 months, and the oldest entry in this database dates to 13 Sep 2024. 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 xmlsec1 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 xmlsec1 for upcoming vulnerabilities?

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