Vulnerability Database · Alpine · Package report

linux-grsec: vulnerability history, versions and safety

linux-grsec is a package in the Alpine ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Apr 2017. 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 U2
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.

Vulert verdict on linux-grsec i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 04 Apr 2017. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 04 Apr 2017 i
  • Highest CVSS 9.8 i
  • With no published fix 0 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 linux-grsec, 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
4.1.20-r0 U2 Yes Details →
4.1.19-r0 U2 Yes Details →
4.1.18-r0 U2 Yes Details →
4.1.17-r1 U2 Yes Details →
4.1.17-r0 U2 Yes Details →
4.1.15-r3 U2 Yes Details →
4.1.15-r2 U2 Yes Details →
4.1.15-r1 U2 Yes Details →
4.1.15-r0 U2 Yes Details →
4.1.13-r0 U2 Yes Details →
4.1.12-r2 U2 Yes Details →
4.1.12-r1 U2 Yes Details →
4.1.12-r0 U2 Yes Details →
4.1.11-r0 U2 Yes Details →
4.1.10-r0 U2 Yes Details →
3.18.21-r1 U2 Yes Details →
3.18.21-r0 U2 Yes Details →
3.18.20-r1 U2 Yes Details →
3.18.20-r0 U2 Yes Details →
3.18.19-r0 U2 Yes Details →
3.18.18-r2 U2 Yes Details →
3.18.18-r1 U2 Yes Details →
3.18.18-r0 U2 Yes Details →
3.18.17-r0 U2 Yes Details →
3.18.16-r0 U2 Yes Details →
3.18.14-r1 U2 Yes Details →
3.18.14-r0 U2 Yes Details →
3.18.13-r0 U2 Yes Details →
3.18.12-r1 U2 Yes Details →
3.18.12-r0 U2 Yes Details →
3.18.11-r3 U2 Yes Details →
3.18.11-r2 U2 Yes Details →
3.18.11-r1 U2 Yes Details →
3.18.11-r0 U2 Yes Details →
3.14.37-r3 U2 Yes Details →
3.14.37-r2 U2 Yes Details →
3.14.37-r1 U2 Yes Details →
3.14.37-r0 U2 Yes Details →
3.14.36-r0 U2 Yes Details →
3.14.35-r0 U2 Yes Details →
3.14.34-r0 U2 Yes Details →
3.14.33-r0 U2 Yes Details →
3.14.32-r0 U2 Yes Details →
3.14.31-r0 U2 Yes Details →
3.14.30-r0 U2 Yes Details →
3.14.29-r1 U2 Yes Details →
3.14.29-r0 U2 Yes Details →
3.14.28-r1 U2 Yes Details →
3.14.28-r0 U2 Yes Details →
3.14.27-r2 U2 Yes Details →
3.14.27-r1 U2 Yes Details →
3.14.27-r0 U2 Yes Details →
3.14.26-r0 U2 Yes Details →
3.14.25-r1 U2 Yes Details →
3.14.25-r0 U2 Yes Details →
3.14.24-r0 U2 Yes Details →
3.14.23-r0 U2 Yes Details →
3.14.22-r1 U2 Yes Details →
3.14.22-r0 U2 Yes Details →
3.14.21-r0 U2 Yes Details →
3.14.20-r2 U2 Yes Details →
3.14.20-r1 U2 Yes Details →
3.14.20-r0 U2 Yes Details →
3.14.19-r3 U2 Yes Details →
3.14.19-r2 U2 Yes Details →
3.14.19-r1 U2 Yes Details →
3.14.19-r0 U2 Yes Details →
3.14.18-r3 U2 Yes Details →
3.14.18-r2 U2 Yes Details →
3.14.18-r1 U2 Yes Details →
3.14.18-r0 U2 Yes Details →
3.14.17-r1 U2 Yes Details →
3.14.17-r0 U2 Yes Details →
3.14.16-r0 U2 Yes Details →
3.14.15-r1 U2 Yes Details →
3.14.15-r0 U2 Yes Details →
3.14.14-r0 U2 Yes Details →
3.14.13-r1 U2 Yes Details →
3.14.13-r0 U2 Yes Details →
3.14.12-r1 U2 Yes Details →
3.14.12-r0 U2 Yes Details →
3.14.11-r2 U2 Yes Details →
3.14.10-r2 U2 Yes Details →
3.14.10-r1 U2 Yes Details →
3.14.8-r1 U2 Yes Details →
3.14.8-r0 U2 Yes Details →
3.14.6-r2 U2 Yes Details →
3.14.6-r1 U2 Yes Details →
3.14.6-r0 U2 Yes Details →
3.14.5-r0 U2 Yes Details →
3.14.4-r2 U2 Yes Details →
3.14.4-r1 U2 Yes Details →
3.14.4-r0 U2 Yes Details →
3.14.2-r0 U2 Yes Details →
3.13.10-r0 U2 Yes Details →
3.13.8-r0 U2 Yes Details →
3.13.7-r0 U2 Yes Details →
3.12.8-r1 U2 Yes Details →
3.12.8-r0 U2 Yes Details →
3.12.7-r1 U2 Yes Details →
3.12.7-r0 U2 Yes Details →
3.12.6-r2 U2 Yes Details →
3.12.6-r1 U2 Yes Details →
3.12.6-r0 U2 Yes Details →
3.12.5-r0 U2 Yes Details →
3.12.4-r0 U2 Yes Details →
3.10.23-r0 U2 Yes Details →
3.10.22-r0 U2 Yes Details →
3.10.21-r0 U2 Yes Details →
3.10.20-r0 U2 Yes Details →
3.10.19-r0 U2 Yes Details →
3.10.18-r2 U2 Yes Details →
3.10.18-r1 U2 Yes Details →
3.10.18-r0 U2 Yes Details →
3.10.17-r2 U2 Yes Details →
3.10.17-r1 U2 Yes Details →
3.10.17-r0 U2 Yes Details →
3.10.16-r0 U2 Yes Details →
3.10.15-r0 U2 Yes Details →
3.10.14-r1 U2 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2

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 linux-grsec

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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 linux-grsec

Is linux-grsec safe to use?

Vulert records 2 vulnerabilities for linux-grsec in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 2 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.

How many vulnerabilities does linux-grsec have?

2 vulnerabilities are recorded for linux-grsec in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 linux-grsec vulnerabilities disclosed?

0 vulnerabilities were recorded for linux-grsec in the last 12 months, and the oldest entry in this database dates to 04 Apr 2017. 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 linux-grsec 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 linux-grsec for upcoming vulnerabilities?

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