VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/ewen-lbh/ffcss: vulnerability history, versions and safety

github.com/ewen-lbh/ffcss is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 24 releases, from Dec 2023 to Aug 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 M1 U1
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 github.com/ewen-lbh/ffcss vulnerabilities

Vulert verdict on github.com/ewen-lbh/ffcss v0.2.0 i

Updated on 23 Oct 2026

Action needed: v0.2.0 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 52/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.2.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 21 Aug 2024 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 48 i
  • OpenSSF scorecard 2/10 i
  • Last release 62 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for github.com/ewen-lbh/ffcss, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20231226220142-15c57e7f7878 26 Dec 2023 M1 U1 GPL-3.0 Yes Details →
v0.2.1-0.20231226220142-15c57e7f7878 26 Dec 2023 M1 U1 GPL-3.0 Yes Details →
v0.2.1-0.20231017202045-f9c491874b85 17 Oct 2023 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20221113150341-5e1ea8f550c6 13 Nov 2022 M1 U1 GPL-3.0 Yes Details →
v0.2.1-0.20221113150341-5e1ea8f550c6 13 Nov 2022 M1 U1 GPL-3.0 Yes Details →
v0.2.1-0.20210918144157-ee7a41ff8307 18 Sep 2021 M1 U1 GPL-3.0 Yes Details →
v0.2.1-0.20210802215122-61107120fde0 02 Aug 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210801160833-e15b87671ba6 01 Aug 2021 M1 U1 GPL-3.0 Yes Details →
v0.2.1-0.20210801160818-d8df7a1126d8 01 Aug 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210729210630-fbf1b2b5f5dd 29 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.2.1-0.20210729210430-e35f4f2bffe9 29 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.2.0 25 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.1.2 10 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.1.2-0.20210709224230-ff107fbf928b 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.1.1 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.1.1-0.20210709191601-15d17d14e6b4 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210709152827-65b42e83a670 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.1.0 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210709143111-9c3a3f8cfbb9 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210709133447-827c42be6a26 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210709132800-263e0db81f53 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210709100735-9ee2a4e71a83 09 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210708204707-871c2b5b1ec6 08 Jul 2021 M1 U1 GPL-3.0 Yes Details →
v0.0.0-20210708181701-17168b8edfdb 08 Jul 2021 M1 U1 GPL-3.0 Yes Details →

All 24 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1

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 github.com/ewen-lbh/ffcss

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-52081: ewen-lbh/ffcss Late-Unicode normalization vulnerability 5.3 medium 0.2.0 28 Dec 2023
CVE-2023-52081: Late-Unicode normalization vulnerability in github.com/ewen-lbh/ffcss N/A unrated 0.2.0 21 Aug 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: 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 github.com/ewen-lbh/ffcss

Is github.com/ewen-lbh/ffcss safe to use?

Vulert records 2 vulnerabilities for github.com/ewen-lbh/ffcss in Go: 0 critical, 0 high, 1 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.

What is github.com/ewen-lbh/ffcss's Vulert package health score?

Vulert scores github.com/ewen-lbh/ffcss 52/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/ewen-lbh/ffcss affected?

Yes. v0.2.0, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/ewen-lbh/ffcss should I use?

v0.2.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/ewen-lbh/ffcss have?

2 vulnerabilities are recorded for github.com/ewen-lbh/ffcss in the Go ecosystem: 0 critical, 0 high, 1 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 github.com/ewen-lbh/ffcss vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/ewen-lbh/ffcss in the last 12 months, and the oldest entry in this database dates to 28 Dec 2023. 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 github.com/ewen-lbh/ffcss 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 github.com/ewen-lbh/ffcss for upcoming vulnerabilities?

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