Vulnerability Database · Packagist · Package report

wallabag/wallabag: vulnerability history, versions and safety

wallabag/wallabag is a package in the Packagist ecosystem. Vulert records 16 vulnerabilities for it across 93 releases, from May 2022 to Apr 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded M16
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 wallabag/wallabag i

Updated on 23 Oct 2026

Careful: one of the 16 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 16 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 16 over 2 years · 0 in the last year i
  • Latest disclosure 09 Apr 2025 i
  • Highest CVSS 6.5 i
  • With no published fix 1 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 wallabag/wallabag, 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
2.6.10 M1 Yes Details →
2.6.9 M1 Yes Details →
2.6.8 M1 Yes Details →
2.6.7 M1 Yes Details →
2.6.6 M2 Yes Details →
2.6.5 M2 Yes Details →
2.6.4 M2 Yes Details →
2.6.3 M2 Yes Details →
2.6.2 M6 Yes Details →
2.6.1 M6 Yes Details →
2.6.0 M6 Yes Details →
2.5.4 M7 No Details →
2.5.3 M11 No Details →
2.5.2 M15 No Details →
2.5.1 M15 No Details →
2.5.0 M15 No Details →
2.4.3 M15 No Details →
2.4.2 M15 No Details →
2.4.1 M15 No Details →
2.4.0 M15 No Details →
2.3.8 M15 No Details →
2.3.7 M15 No Details →
2.3.6 M15 No Details →
2.3.5 M15 No Details →
2.3.4 M15 No Details →
2.3.3 M15 No Details →
2.3.2 M16 No Details →
2.3.1 M16 No Details →
2.3.0 M16 No Details →
2.2.3 M16 No Details →
2.2.2 M15 No Details →
2.2.1 M15 No Details →
2.2.0 M15 No Details →
2.1.6.1 M15 No Details →
2.1.6 M15 No Details →
2.1.5 M15 No Details →
2.1.4 M15 No Details →
2.1.3 M15 No Details →
2.1.2 M15 No Details →
2.1.1 M15 No Details →
2.1.0 M15 No Details →
2.0.8 M15 No Details →
2.0.7 M15 No Details →
2.0.6 M15 No Details →
2.0.5 M15 No Details →
2.0.4 M15 No Details →
2.0.3 M15 No Details →
2.0.2 M15 No Details →
2.0.1 M15 No Details →
2.0.0 M15 No Details →
2.0.0-beta.2 M15 No Details →
2.0.0-beta.1 M15 No Details →
2.0.0-alpha.2 M13 No Details →
2.0.0-alpha.1 M13 No Details →
2.0.0-alpha.0 M6 No Details →
1.9.2 M6 No Details →
1.9.1 M6 No Details →
1.9.1beta3 M6 No Details →
1.9.1beta2 M6 No Details →
1.9.1beta1 M6 No Details →
1.9.1-b M6 No Details →
1.9.1alpha2 M6 No Details →
1.9.1alpha1 M6 No Details →
1.9 M6 No Details →
1.9RC1 M6 No Details →
1.9beta2 M6 No Details →
1.9beta M6 No Details →
1.8.1 M6 No Details →
1.8.1b M6 No Details →
1.8.0 M6 No Details →
1.7.2 M6 No Details →
1.7.1 M6 No Details →
1.7.0 M6 No Details →
1.6.1 M6 No Details →
1.6.1b M6 No Details →
1.6.0 M6 No Details →
1.5.2 M6 No Details →
1.5.1.1 M6 No Details →
1.5.1 M6 No Details →
1.5.0 M6 No Details →
1.4.0 M6 No Details →
1.3.1 M6 No Details →
1.3.0 M6 No Details →
1.2.0 M6 No Details →
1.1.0 M6 No Details →
1.0.0 M6 No Details →
1.0-beta5.2 M6 No Details →
1.0-beta5.1 M6 No Details →
1.0-beta5 M6 No Details →
1.0-beta4 M6 No Details →
1.0-beta3 M6 No Details →
1.0-beta2 M6 No Details →
1.0-beta1 M6 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 13
  • 2024 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for wallabag/wallabag

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 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 wallabag/wallabag

Is wallabag/wallabag safe to use?

Vulert records 16 vulnerabilities for wallabag/wallabag in Packagist: 0 critical, 0 high, 16 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does wallabag/wallabag have?

16 vulnerabilities are recorded for wallabag/wallabag in the Packagist ecosystem: 0 critical, 0 high, 16 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 wallabag/wallabag vulnerabilities disclosed?

0 vulnerabilities were recorded for wallabag/wallabag in the last 12 months, and the oldest entry in this database dates to 14 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 wallabag/wallabag 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 wallabag/wallabag for upcoming vulnerabilities?

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