Vulnerability Database · Packagist · Package report

yab/quarx: vulnerability history, versions and safety

yab/quarx is a package in the Packagist ecosystem. Vulert records 1 vulnerability for it across 116 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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.

Vulert verdict on yab/quarx i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 1 vulnerability 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 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 6.1 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

Every version Vulert holds for yab/quarx, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
v2.4.4 M1 Yes Details →
v2.4.3 M1 Yes Details →
v2.4.2 M1 Yes Details →
v2.4.1 M1 Yes Details →
v2.4.0 M1 Yes Details →
v2.3.32 M1 Yes Details →
v2.3.31 M1 Yes Details →
v2.3.30 M1 Yes Details →
v2.3.29 M1 Yes Details →
v2.3.28 M1 Yes Details →
v2.3.27 M1 Yes Details →
v2.3.26 M1 Yes Details →
v2.3.25 M1 Yes Details →
v2.3.24 M1 Yes Details →
v2.3.23 M1 Yes Details →
v2.3.22 M1 Yes Details →
v2.3.21 M1 Yes Details →
v2.3.20 M1 Yes Details →
v2.3.19 M1 Yes Details →
v2.3.18 M1 Yes Details →
v2.3.17 M1 Yes Details →
v2.3.16 M1 Yes Details →
v2.3.15 M1 Yes Details →
v2.3.14 M1 Yes Details →
v2.3.13 M1 Yes Details →
v2.3.12 M1 Yes Details →
v2.3.11 M1 Yes Details →
v2.3.10 M1 Yes Details →
v2.3.9 M1 Yes Details →
v2.3.8 M1 Yes Details →
v2.3.7 M1 Yes Details →
v2.3.6 M1 Yes Details →
v2.3.5 M1 Yes Details →
v2.3.4 M1 Yes Details →
v2.3.3 M1 Yes Details →
v2.3.2 M1 Yes Details →
v2.3.1 M1 Yes Details →
v2.3.0 M1 Yes Details →
v2.2.12 M1 Yes Details →
v2.2.11 M1 Yes Details →
v2.2.10 M1 Yes Details →
v2.2.9 M1 Yes Details →
v2.2.8 M1 Yes Details →
v2.2.7 M1 Yes Details →
v2.2.6 M1 Yes Details →
v2.2.5 M1 Yes Details →
v2.2.4 M1 Yes Details →
v2.2.3 M1 Yes Details →
v2.2.2 M1 Yes Details →
v2.2.1 M1 Yes Details →
v2.2.0 M1 Yes Details →
v2.1.3 M1 Yes Details →
v2.1.2 M1 Yes Details →
v2.1.1 M1 Yes Details →
v2.1.0 M1 Yes Details →
v2.0.1 M1 Yes Details →
v2.0.0 M1 Yes Details →
v1.4.24 M1 Yes Details →
v1.4.23 M1 Yes Details →
v1.4.22 M1 Yes Details →
v1.4.21 M1 Yes Details →
v1.4.20 M1 Yes Details →
v1.4.19 M1 Yes Details →
v1.4.18 M1 Yes Details →
v1.4.17 M1 Yes Details →
v1.4.16 M1 Yes Details →
v1.4.15 M1 Yes Details →
v1.4.14 M1 Yes Details →
v1.4.13 M1 Yes Details →
v1.4.12 M1 Yes Details →
v1.4.11 M1 Yes Details →
v1.4.10 M1 Yes Details →
v1.4.9 M1 Yes Details →
v1.4.8 M1 Yes Details →
v1.4.7 M1 Yes Details →
v1.4.6 M1 Yes Details →
v1.4.5 M1 Yes Details →
v1.4.4 M1 Yes Details →
v1.4.3 M1 Yes Details →
v1.4.2 M1 Yes Details →
v1.4.1 M1 Yes Details →
v1.4.0 M1 Yes Details →
v1.3.6 M1 Yes Details →
v1.3.5 M1 Yes Details →
v1.3.4 M1 Yes Details →
v1.3.3 M1 Yes Details →
v1.3.2 M1 Yes Details →
v1.3.1 M1 Yes Details →
v1.3.0 M1 Yes Details →
v1.2.0 M1 Yes Details →
v1.1.0 M1 Yes Details →
v1.0.5 M1 Yes Details →
v1.0.4 M1 Yes Details →
v1.0.3 M1 Yes Details →
v1.0.2 M1 Yes Details →
v1.0.1 M1 Yes Details →
v1.0.0 M1 Yes Details →
v0.7.0 M1 Yes Details →
v0.6.6 M1 Yes Details →
v0.6.5 M1 Yes Details →
v0.6.4 M1 Yes Details →
v0.6.3 M1 Yes Details →
v0.6.2 M1 Yes Details →
v0.6.1 M1 Yes Details →
v0.6.0 M1 Yes Details →
v0.5.0 M1 Yes Details →
v0.4.0 M1 Yes Details →
v0.3.1 M1 Yes Details →
v0.3.0 M1 Yes Details →
v0.2.1 M1 Yes Details →
v0.2.0 M1 Yes Details →
v0.1.5 M1 Yes Details →
v0.1.4 M1 Yes Details →
v0.1.3 M1 Yes Details →
v0.1.2 M1 Yes Details →
v0.1.1 M1 Yes Details →

Newest 116 of 116 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for yab/quarx

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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

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 yab/quarx

Is yab/quarx safe to use?

Vulert records 1 vulnerabilities for yab/quarx in Packagist: 0 critical, 0 high, 1 medium and 0 low. 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 yab/quarx have?

1 vulnerability is recorded for yab/quarx in the Packagist ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new yab/quarx vulnerabilities disclosed?

0 vulnerabilities were recorded for yab/quarx in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 yab/quarx 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 yab/quarx for upcoming vulnerabilities?

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