VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/leanote/leanote: vulnerability history, versions and safety

github.com/leanote/leanote is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 5 releases, first recorded in Dec 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
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.

See all github.com/leanote/leanote vulnerabilities

Vulert verdict on github.com/leanote/leanote v0.0.0-20210815023534-d58fd6434f9d i

Updated on 23 Oct 2026

Careful: v0.0.0-20210815023534-d58fd6434f9d has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.0.0-20210815023534-d58fd6434f9d — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 21 Dec 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i
  • Stars 11,674 i
  • OpenSSF scorecard 1/10 i
  • Last release 62 months ago i
  • Licence LGPL-3.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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/leanote/leanote, 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-20210815023534-d58fd6434f9d 15 Aug 2021 M1 LGPL-3.0 No Details →
v0.0.0-20190409094444-5e61291703a8 09 Apr 2019 M1 GPL-2.0-or-later No Details →
v0.0.0-20181207094038-e4b585633854 07 Dec 2018 M1 GPL-2.0-or-later No Details →
v0.0.0-20180308032105-340df9ce16ee 08 Mar 2018 M1 GPL-2.0-or-later No Details →
v0.0.0-20170220055724-41f95cf0e577 20 Feb 2017 M1 GPL-2.0-or-later No Details →

All 5 versions Vulert tracks for this package. 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 github.com/leanote/leanote

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Leanote Cross-Site Scripting Vulnerability (CVE-2021-4263) 6.1 medium No fix published 21 Dec 2022

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/leanote/leanote

Is github.com/leanote/leanote safe to use?

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

What is github.com/leanote/leanote's Vulert package health score?

Vulert scores github.com/leanote/leanote 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/leanote/leanote affected?

Yes. v0.0.0-20210815023534-d58fd6434f9d, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/leanote/leanote should I use?

v0.0.0-20210815023534-d58fd6434f9d 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/leanote/leanote have?

1 vulnerability is recorded for github.com/leanote/leanote in the Go 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 github.com/leanote/leanote vulnerabilities disclosed?

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

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