VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

aahframe.work: vulnerability history, versions and safety

aahframe.work is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 72 releases, first recorded in Apr 2021. 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 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 aahframe.work vulnerabilities

Vulert verdict on aahframe.work v0.12.5 i

Updated on 23 Oct 2026

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

Package health score 62/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • 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.12.5 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 14 Apr 2021 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 683 i
  • OpenSSF scorecard 1/10 i
  • Last release 79 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 aahframe.work, 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.12.4-0.20200902023120-f42ff581c627 02 Sep 2020 U1 MIT Yes Details →
v0.12.4-0.20200902022733-0bf594d222fb 02 Sep 2020 U1 MIT Yes Details →
v0.12.5 04 Mar 2020 U1 MIT Yes Details →
v0.12.4 03 Mar 2020 U1 MIT Yes Details →
v0.12.4-0.20191012075708-0b83e7ed5964 12 Oct 2019 U1 MIT Yes Details →
v0.12.4-0.20191010074013-bcc746ad1a37 10 Oct 2019 U1 MIT Yes Details →
v0.12.4-0.20191009221746-732389bca06d 09 Oct 2019 U1 MIT Yes Details →
v0.12.4-0.20191009214941-c50a16521de9 09 Oct 2019 U1 MIT Yes Details →
v0.12.4-0.20191009210745-a15490d3fad2 09 Oct 2019 U1 MIT Yes Details →
v0.12.4-0.20191009203450-71be3bb69f69 09 Oct 2019 U1 MIT Yes Details →
v0.12.4-0.20190922181227-0bcfe2c6ffef 22 Sep 2019 U1 MIT Yes Details →
v0.12.3-0.20190515074852-02bb60192b40 15 May 2019 U1 MIT Yes Details →
v0.12.4-0.20190515074852-02bb60192b40 15 May 2019 U1 MIT Yes Details →
v0.12.4-0.20190515073616-5071f8ef0cee 15 May 2019 U1 MIT Yes Details →
v0.12.4-0.20190207070122-10bda73185a9 07 Feb 2019 U1 MIT Yes Details →
v0.12.3 07 Feb 2019 U1 MIT Yes Details →
v0.12.2-0.20190206113033-3374b69984a0 06 Feb 2019 U1 MIT Yes Details →
v0.12.2-0.20190206063112-205d56ee0645 06 Feb 2019 U1 MIT Yes Details →
v0.12.2-0.20190115081053-8c6544f49098 15 Jan 2019 U1 MIT Yes Details →
v0.12.2-0.20190115081005-59fcd5938847 15 Jan 2019 U1 MIT Yes Details →
v0.12.2-0.20190115074640-7c32af630238 15 Jan 2019 U1 MIT Yes Details →
v0.12.2-0.20190113060207-413b805e1ee4 13 Jan 2019 U1 MIT Yes Details →
v0.12.2-0.20190111183604-b1a2826abfb3 11 Jan 2019 U1 MIT Yes Details →
v0.12.2-0.20181228092204-def7ed088796 28 Dec 2018 U1 MIT Yes Details →
v0.12.2 13 Dec 2018 U1 MIT Yes Details →
v0.12.2-0.20181213075607-1684965f3d96 13 Dec 2018 U1 MIT Yes Details →
v0.12.2-0.20181213075607-53a54a200360 13 Dec 2018 U1 MIT Yes Details →
v0.12.2-0.20181213074249-31fcc59b0c4a 13 Dec 2018 U1 MIT Yes Details →
v0.12.2-0.20181208073620-3a57ff0569b1 08 Dec 2018 U1 MIT Yes Details →
v0.12.1 08 Dec 2018 U1 MIT Yes Details →
v0.12.1-0.20181208073442-954c08a236c7 08 Dec 2018 U1 MIT Yes Details →
v0.11.5-0.20181208072334-f19d32344a82 08 Dec 2018 U1 MIT Yes Details →
v0.11.5-0.20181208071048-1134abeefeb5 08 Dec 2018 U1 MIT Yes Details →
v0.12.0 02 Dec 2018 U1 MIT Yes Details →
v0.11.5-0.20181202162942-d8e86b90dd8b 02 Dec 2018 U1 MIT Yes Details →
v0.11.4-0.20181202162731-366e48b22a7d 02 Dec 2018 U1 MIT Yes Details →
v0.11.4-0.20181202102419-bcb64a32602d 02 Dec 2018 U1 MIT Yes Details →
v0.11.4-0.20181202101818-09a7f41bde8e 02 Dec 2018 U1 MIT Yes Details →
v0.11.4-0.20181202100524-15c96a0bedfd 02 Dec 2018 U1 MIT Yes Details →
v0.11.4-0.20181202091310-44eb3f8f6fed 02 Dec 2018 U1 MIT Yes Details →
v0.11.4-0.20181202075643-9da1180e86b6 02 Dec 2018 U1 MIT Yes Details →
v0.0.0-20181126051259-b64fdc6b18f6 26 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181123084832-12d68cfdf37f 23 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181118102313-e72e489dc0f4 18 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181116070044-7e8c1f894ed3 16 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181115105319-0e588ecb959d 15 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181107055009-195a7577b123 07 Nov 2018 U1 MIT Yes Details →
v0.0.0-20181103212526-cd7b92071338 03 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181103212526-cd7b92071338 03 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181103212322-91f16961c11f 03 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102063233-b2d4cadf425f 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102063158-07737138c446 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102063146-7960c421a966 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102063138-3a3578239b05 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102063055-b9d577d4512d 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102063043-2c8906da5d0d 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102063027-ad8016db0c4e 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102062853-34c5e120b169 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102062828-a8dee262ffca 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102062818-25d002ed8acd 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102062745-e4f23f6983b1 02 Nov 2018 U1 MIT Yes Details →
v0.11.4-0.20181102062717-ab216ea3d26e 02 Nov 2018 U1 MIT Yes Details →
v0.0.0-20181013054310-9873edb08c38 13 Oct 2018 U1 MIT Yes Details →
v0.11.4 28 Aug 2018 U1 MIT Yes Details →
v0.11.3 18 Aug 2018 U1 MIT Yes Details →
v0.11.2 28 Jul 2018 U1 MIT Yes Details →
v0.11.1 22 Jul 2018 U1 MIT Yes Details →
v0.11.0 07 Jul 2018 U1 MIT Yes Details →
v0.10.1 24 Apr 2018 U1 MIT Yes Details →
v0.5.1 21 May 2017 U1 MIT Yes Details →
v0.4.1 15 Apr 2017 U1 MIT Yes Details →
v0.0.0-20160704040534-43507327c421 04 Jul 2016 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 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 aahframe.work

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-36559: Path Traversal in aahframe.work N/A unrated 0.12.4 14 Apr 2021

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 aahframe.work

Is aahframe.work safe to use?

Vulert records 1 vulnerabilities for aahframe.work in Go: 0 critical, 0 high, 0 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 aahframe.work's Vulert package health score?

Vulert scores aahframe.work 62/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 aahframe.work affected?

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

Which version of aahframe.work should I use?

v0.12.5 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 aahframe.work have?

1 vulnerability is recorded for aahframe.work in the Go ecosystem: 0 critical, 0 high, 0 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 aahframe.work vulnerabilities disclosed?

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

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