VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/jessfraz/pastebinit: vulnerability history, versions and safety

github.com/jessfraz/pastebinit is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 6 releases, from Dec 2022 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/jessfraz/pastebinit vulnerabilities

Vulert verdict on github.com/jessfraz/pastebinit v0.2.4 i

Updated on 23 Oct 2026

Action needed: v0.2.4 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 57/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • 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.4 — 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 73 i
  • OpenSSF scorecard 2/10 i
  • Last release 96 months ago i
  • Licence MIT 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/jessfraz/pastebinit, 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.2.5-0.20200917211952-f38bc3ad5e4d 17 Sep 2020 M1 U1 MIT Yes Details →
v0.2.5-0.20190525201104-f6c5b1df4e01 25 May 2019 M1 U1 MIT Yes Details →
v0.2.4 25 Sep 2018 M1 U1 MIT Yes Details →
v0.2.3 18 Jul 2018 M1 U1 MIT Yes Details →
v0.2.2 17 Jul 2018 M1 U1 MIT Yes Details →
v0.2.1 14 Jul 2018 M1 U1 MIT Yes Details →

All 6 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
  • 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/jessfraz/pastebinit

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-25059: pastebinit Path Traversal vulnerability 5.3 medium 0.2.3 30 Dec 2022
CVE-2018-25059: Path Traversal vulnerability in pastebinit N/A unrated 0.2.3 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/jessfraz/pastebinit

Is github.com/jessfraz/pastebinit safe to use?

Vulert records 2 vulnerabilities for github.com/jessfraz/pastebinit 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/jessfraz/pastebinit's Vulert package health score?

Vulert scores github.com/jessfraz/pastebinit 57/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/jessfraz/pastebinit affected?

Yes. v0.2.4, 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/jessfraz/pastebinit should I use?

v0.2.4 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/jessfraz/pastebinit have?

2 vulnerabilities are recorded for github.com/jessfraz/pastebinit 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/jessfraz/pastebinit vulnerabilities disclosed?

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

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