VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/labring/sealos: vulnerability history, versions and safety

github.com/labring/sealos is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Jun 2023. 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 C1 H1
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/labring/sealos vulnerabilities

Vulert verdict on github.com/labring/sealos v5.1.1+incompatible i

Updated on 23 Oct 2026

Careful: v5.1.1+incompatible has 2 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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 v5.1.1+incompatible — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 30 Jun 2023 i
  • Highest CVSS 9.9 i
  • With no published fix 1 i
  • Stars 18,370 i
  • Last release 11 months ago i
  • Licence non-standard 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/labring/sealos, 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-20261014071130-fc000c1dc17b 14 Oct 2026 C1 H1 — No Details →
v5.1.1-0.20261014071130-fc000c1dc17b+incompatible 14 Oct 2026 C1 H1 — No Details →
v0.0.0-20261014040443-e819ef6de78c 14 Oct 2026 C1 H1 — No Details →
v5.1.1-0.20261014040443-e819ef6de78c+incompatible 14 Oct 2026 C1 H1 — No Details →
v0.0.0-20261012070221-74bf2df06c26 12 Oct 2026 C1 H1 — No Details →
v5.1.1-0.20261012070221-74bf2df06c26+incompatible 12 Oct 2026 C1 H1 — No Details →
v5.1.2-rc6.0.20261009035058-e630e042c3be+incompatible 09 Oct 2026 C1 H1 — No Details →
v0.0.0-20261009034713-83d1278086c0 09 Oct 2026 C1 H1 — No Details →
v5.1.1-0.20261009034713-83d1278086c0+incompatible 09 Oct 2026 C1 H1 — No Details →
v0.0.0-20261009032627-36ad4110d393 09 Oct 2026 C1 H1 — No Details →
v5.1.1-0.20261009032627-36ad4110d393+incompatible 09 Oct 2026 C1 H1 — No Details →
v0.0.0-20261009032204-fa0fbc712418 09 Oct 2026 C1 H1 — No Details →
v0.0.0-20261008102209-9ca3fef3c1c8 08 Oct 2026 C1 H1 — No Details →
v5.1.1-0.20261008102209-9ca3fef3c1c8+incompatible 08 Oct 2026 C1 H1 — No Details →
v0.0.0-20261008080704-68bfa4bce93a 08 Oct 2026 C1 H1 — No Details →
v5.1.1-0.20261008080704-68bfa4bce93a+incompatible 08 Oct 2026 C1 H1 — No Details →
v0.0.0-20260928092302-d92ef316ba41 28 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260928092302-d92ef316ba41+incompatible 28 Sep 2026 C1 H1 — No Details →
v0.0.0-20260928035236-f945413f2b1f 28 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260928035236-f945413f2b1f+incompatible 28 Sep 2026 C1 H1 — No Details →
v0.0.0-20260918024339-6410f204a2a1 18 Sep 2026 C1 H1 — No Details →
v0.0.0-20260917092243-a6690be270ce 17 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260917092243-a6690be270ce+incompatible 17 Sep 2026 C1 H1 — No Details →
v0.0.0-20260914092933-ab6788b8c46d 14 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260914092933-ab6788b8c46d+incompatible 14 Sep 2026 C1 H1 — No Details →
v0.0.0-20260912080220-1e97ffc47589 12 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260912080220-1e97ffc47589+incompatible 12 Sep 2026 C1 H1 — No Details →
v0.0.0-20260908023709-95c027dbcb25 08 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260908023709-95c027dbcb25+incompatible 08 Sep 2026 C1 H1 — No Details →
v0.0.0-20260908021053-317ed32925ac 08 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260908021053-317ed32925ac+incompatible 08 Sep 2026 C1 H1 — No Details →
v0.0.0-20260907034335-30669519c434 07 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260907034335-30669519c434+incompatible 07 Sep 2026 C1 H1 — No Details →
v0.0.0-20260907033903-dc1fa3a85358 07 Sep 2026 C1 H1 — No Details →
v0.0.0-20260904074829-86ee123c1d61 04 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260904074829-86ee123c1d61+incompatible 04 Sep 2026 C1 H1 — No Details →
v0.0.0-20260904070506-2029b9be138c 04 Sep 2026 C1 H1 — No Details →
v0.0.0-20260904062750-463143b2c0ab 04 Sep 2026 C1 H1 — No Details →
v0.0.0-20260903145018-9d02df00c4ba 03 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260903145018-9d02df00c4ba+incompatible 03 Sep 2026 C1 H1 — No Details →
v0.0.0-20260903113909-bcb6870bdee9 03 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260903113909-bcb6870bdee9+incompatible 03 Sep 2026 C1 H1 — No Details →
v0.0.0-20260903100438-17aebfa53188 03 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260903100438-17aebfa53188+incompatible 03 Sep 2026 C1 H1 — No Details →
v0.0.0-20260903092315-da2fd8617120 03 Sep 2026 C1 H1 — No Details →
v0.0.0-20260903040130-e0013e883bfe 03 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260903040130-e0013e883bfe+incompatible 03 Sep 2026 C1 H1 — No Details →
v0.0.0-20260902093634-86c24b661926 02 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260902093634-86c24b661926+incompatible 02 Sep 2026 C1 H1 — No Details →
v0.0.0-20260902090123-e99acfb765e1 02 Sep 2026 C1 H1 — No Details →
v5.1.1-0.20260902090123-e99acfb765e1+incompatible 02 Sep 2026 C1 H1 — No Details →
v0.0.0-20260902040235-b242ab75bc1b 02 Sep 2026 C1 H1 — No Details →
v0.0.0-20260901031247-6c78169a8fb3 01 Sep 2026 C1 H1 — No Details →
v0.0.0-20260831024852-31d9e1dcc8d3 31 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260831024852-31d9e1dcc8d3+incompatible 31 Aug 2026 C1 H1 — No Details →
v0.0.0-20260828104458-5d0ecb469881 28 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260828104458-5d0ecb469881+incompatible 28 Aug 2026 C1 H1 — No Details →
v0.0.0-20260828084635-2586ffd27af9 28 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260828084635-2586ffd27af9+incompatible 28 Aug 2026 C1 H1 — No Details →
v0.0.0-20260828080903-70ac4e999b62 28 Aug 2026 C1 H1 — No Details →
v0.0.0-20260828074419-553ef241a987 28 Aug 2026 C1 H1 — No Details →
v0.0.0-20260828024437-d859f43238f3 28 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260828024437-d859f43238f3+incompatible 28 Aug 2026 C1 H1 — No Details →
v0.0.0-20260827085109-b3dcab4119a5 27 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260827085109-b3dcab4119a5+incompatible 27 Aug 2026 C1 H1 — No Details →
v0.0.0-20260827082740-91c24c746380 27 Aug 2026 C1 H1 — No Details →
v0.0.0-20260827082219-a2a338dbcf07 27 Aug 2026 C1 H1 — No Details →
v0.0.0-20260826141459-8526c3a03057 26 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260826141459-8526c3a03057+incompatible 26 Aug 2026 C1 H1 — No Details →
v0.0.0-20260826115116-7afc77ef3dc9 26 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260826115116-7afc77ef3dc9+incompatible 26 Aug 2026 C1 H1 — No Details →
v0.0.0-20260821070538-beea1e56cb33 21 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260821070538-beea1e56cb33+incompatible 21 Aug 2026 C1 H1 — No Details →
v0.0.0-20260821065433-b53b60d7bbca 21 Aug 2026 C1 H1 — No Details →
v0.0.0-20260821031819-c82addbaa2a9 21 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260821031819-c82addbaa2a9+incompatible 21 Aug 2026 C1 H1 — No Details →
v0.0.0-20260820095457-228e59250cdc 20 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260820095457-228e59250cdc+incompatible 20 Aug 2026 C1 H1 — No Details →
v0.0.0-20260820033726-c1ce22d06f0d 20 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260820033726-c1ce22d06f0d+incompatible 20 Aug 2026 C1 H1 — No Details →
v0.0.0-20260819095609-03425c6a7c62 19 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260819095609-03425c6a7c62+incompatible 19 Aug 2026 C1 H1 — No Details →
v0.0.0-20260819021931-3cffcaacd3b9 19 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260819021931-3cffcaacd3b9+incompatible 19 Aug 2026 C1 H1 — No Details →
v0.0.0-20260818072149-95c67c41eb31 18 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260818072149-95c67c41eb31+incompatible 18 Aug 2026 C1 H1 — No Details →
v0.0.0-20260818032651-a706e3297ae8 18 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260818032651-a706e3297ae8+incompatible 18 Aug 2026 C1 H1 — No Details →
v5.1.2-rc6+incompatible 16 Aug 2026 C1 H1 — No Details →
v0.0.0-20260813083909-a04e0eb544b9 13 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260813083909-a04e0eb544b9+incompatible 13 Aug 2026 C1 H1 — No Details →
v0.0.0-20260811110740-cc8ebb874306 11 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260811110740-cc8ebb874306+incompatible 11 Aug 2026 C1 H1 — No Details →
v0.0.0-20260811105832-82a30ff42d81 11 Aug 2026 C1 H1 — No Details →
v0.0.0-20260811062014-54e6c1da3de0 11 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260811062014-54e6c1da3de0+incompatible 11 Aug 2026 C1 H1 — No Details →
v0.0.0-20260810034733-ec6ad8da2f01 10 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260810034733-ec6ad8da2f01+incompatible 10 Aug 2026 C1 H1 — No Details →
v0.0.0-20260806095045-13d3350e5b61 06 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260806095045-13d3350e5b61+incompatible 06 Aug 2026 C1 H1 — No Details →
v0.0.0-20260806020316-cf6f27d8aa86 06 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260806020316-cf6f27d8aa86+incompatible 06 Aug 2026 C1 H1 — No Details →
v0.0.0-20260804074411-c2dd5ccc40cd 04 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260804074411-c2dd5ccc40cd+incompatible 04 Aug 2026 C1 H1 — No Details →
v0.0.0-20260804024559-a0fb462148ee 04 Aug 2026 C1 H1 — No Details →
v0.0.0-20260803085251-6c28b33cd8d8 03 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260803085251-6c28b33cd8d8+incompatible 03 Aug 2026 C1 H1 — No Details →
v0.0.0-20260803070349-78bf640d3070 03 Aug 2026 C1 H1 — No Details →
v5.1.1-0.20260803070349-78bf640d3070+incompatible 03 Aug 2026 C1 H1 — No Details →
v0.0.0-20260731092046-46682b102367 31 Jul 2026 C1 H1 — No Details →
v5.1.1-0.20260731092046-46682b102367+incompatible 31 Jul 2026 C1 H1 — No Details →
v0.0.0-20260731082143-15ad047b7a66 31 Jul 2026 C1 H1 — No Details →
v5.1.1-0.20260731082143-15ad047b7a66+incompatible 31 Jul 2026 C1 H1 — No Details →
v0.0.0-20260729084855-f841fedada1b 29 Jul 2026 C1 H1 — No Details →
v5.1.1-0.20260729084855-f841fedada1b+incompatible 29 Jul 2026 C1 H1 — No Details →
v0.0.0-20260729063733-9fedc50c05c3 29 Jul 2026 C1 H1 — No Details →
v5.1.1-0.20260729063733-9fedc50c05c3+incompatible 29 Jul 2026 C1 H1 — No Details →
v0.0.0-20260728075745-3aa8b3ebfa44 28 Jul 2026 C1 H1 — No Details →
v5.1.1-0.20260728075745-3aa8b3ebfa44+incompatible 28 Jul 2026 C1 H1 — No Details →
v0.0.0-20260728063656-da3b7b6c03a8 28 Jul 2026 C1 H1 — No Details →

The newest 120 of 736 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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 github.com/labring/sealos

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-33190: Improper Configuration of RBAC Permissions in Sealos 9.9 critical 4.2.1-rc4 30 Jun 2023
CVE-2023-36815: Sealos billing system permission control defect 7.3 high No fix published 30 Jun 2023

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/labring/sealos

Is github.com/labring/sealos safe to use?

Vulert records 2 vulnerabilities for github.com/labring/sealos in Go: 1 critical, 1 high, 0 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/labring/sealos's Vulert package health score?

Vulert scores github.com/labring/sealos 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/labring/sealos affected?

Yes. v5.1.1+incompatible, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/labring/sealos should I use?

v5.1.1+incompatible 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/labring/sealos have?

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

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

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