Vulnerability Database · PyPI · Package report

skyvern: vulnerability history, versions and safety

skyvern is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 84 releases, from Jun 2025 to Jul 2026. 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 H1 U1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on skyvern 1.0.56 i

Updated on 23 Oct 2026

Careful: 1.0.56 has 2 known vulnerabilities, and 2 have 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 Widely used
  • 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 1.0.56 — affected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.5 i
  • With no published fix 2 i
  • Depended on by 3 packages i
  • Stars 23,219 i
  • Last release this month i
  • Licence AGPL-3.0 i

Version list, release dates, licence and dependants published by PyPI, 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 skyvern, 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
1.0.56 14 Oct 2026 H1 U1 — No Details →
1.0.55 01 Oct 2026 H1 U1 — No Details →
1.0.48 05 Aug 2026 H1 U1 — No Details →
1.0.47 16 Jul 2026 H1 U1 — No Details →
1.0.46 08 Jul 2026 H1 U1 — No Details →
1.0.45 07 Jul 2026 H1 U1 — No Details →
1.0.44 30 Jun 2026 H1 U1 — No Details →
1.0.43 18 Jun 2026 H1 U1 — No Details →
1.0.42 18 Jun 2026 H1 U1 — No Details →
1.0.41 11 Jun 2026 H1 U1 — No Details →
1.0.40 10 Jun 2026 H1 U1 — No Details →
1.0.37 31 May 2026 H1 U1 — No Details →
1.0.36 10 May 2026 H1 U1 — No Details →
1.0.35 08 May 2026 H1 U1 — No Details →
1.0.34 07 May 2026 H1 U1 — No Details →
1.0.33 07 May 2026 H1 U1 — No Details →
1.0.32 01 May 2026 H1 U1 — No Details →
1.0.31 14 Apr 2026 H1 U1 — No Details →
1.0.30 08 Apr 2026 H1 U1 — No Details →
1.0.29 02 Apr 2026 H1 U1 — No Details →
1.0.28 25 Mar 2026 H1 U1 — No Details →
1.0.27 25 Mar 2026 H1 U1 — No Details →
1.0.26 25 Mar 2026 H1 U1 — No Details →
1.0.25 24 Mar 2026 H1 U1 — No Details →
1.0.24 13 Mar 2026 H1 U1 — No Details →
1.0.23 02 Mar 2026 H1 U1 — No Details →
1.0.22 26 Feb 2026 H1 U1 — No Details →
1.0.21 24 Feb 2026 H1 U1 — No Details →
1.0.20 21 Feb 2026 H1 U1 — No Details →
1.0.19 20 Feb 2026 H1 U1 — No Details →
1.0.18 20 Feb 2026 H1 U1 — No Details →
1.0.17 19 Feb 2026 H1 U1 — No Details →
1.0.16 19 Feb 2026 H1 U1 — No Details →
1.0.15 18 Feb 2026 H1 U1 — No Details →
1.0.14 18 Feb 2026 H1 U1 — No Details →
1.0.13 10 Feb 2026 H1 U1 — No Details →
1.0.12 03 Feb 2026 H1 U1 — No Details →
1.0.11 29 Jan 2026 H1 U1 — No Details →
1.0.10 26 Jan 2026 H1 U1 — No Details →
1.0.6 19 Dec 2025 H1 U1 — No Details →
1.0.3 12 Dec 2025 H1 U1 — No Details →
1.0.2 03 Dec 2025 H1 U1 — No Details →
1.0.1 24 Nov 2025 H1 U1 — No Details →
1.0.0 15 Nov 2025 H1 U1 — No Details →
0.2.23 11 Nov 2025 H1 U1 — No Details →
0.2.22 07 Nov 2025 H1 U1 — No Details →
0.2.21 29 Oct 2025 H1 U1 — No Details →
0.2.20 25 Oct 2025 H1 U1 — No Details →
0.2.19 24 Oct 2025 H1 U1 — No Details →
0.2.18 23 Oct 2025 H1 U1 — No Details →
0.2.17 16 Oct 2025 H1 U1 — No Details →
0.2.16 01 Oct 2025 H1 U1 — No Details →
0.2.6 23 Jul 2025 H1 U1 — No Details →
0.2.5 15 Jul 2025 H1 U1 — No Details →
0.2.1 10 Jun 2025 H1 U1 — No Details →
0.2.0 29 May 2025 H1 U1 — No Details →
0.1.89 29 May 2025 H1 U1 — No Details →
0.1.88 28 May 2025 H1 U1 — No Details →
0.1.86 28 May 2025 H1 U1 — No Details →
0.1.85 22 May 2025 H1 U1 — No Details →
0.1.84 19 May 2025 H1 U1 — No Details →
0.1.83 18 May 2025 H1 U1 — No Details →
0.1.82 15 May 2025 H1 U1 — No Details →
0.1.81 06 May 2025 H1 U1 — No Details →
0.1.79 30 Apr 2025 H1 U1 — No Details →
0.1.78 23 Apr 2025 H1 U1 — No Details →
0.1.77 18 Apr 2025 H1 U1 — No Details →
0.1.76 12 Apr 2025 H1 U1 — No Details →
0.1.75 12 Apr 2025 H1 U1 — No Details →
0.1.74 11 Apr 2025 H1 U1 — No Details →
0.1.73 03 Apr 2025 H1 U1 — No Details →
0.1.72 03 Apr 2025 H1 U1 — No Details →
0.1.71 03 Apr 2025 H1 U1 — No Details →
0.1.70 03 Apr 2025 H1 U1 — No Details →
0.1.69 02 Apr 2025 H1 U1 — No Details →
0.1.68 01 Apr 2025 H1 U1 — No Details →
0.1.67 01 Apr 2025 H1 U1 — No Details →
0.1.66 01 Apr 2025 H1 U1 — No Details →
0.1.64 17 Mar 2025 H1 U1 — No Details →
0.1.63 17 Mar 2025 H1 U1 — No Details →
0.1.62 17 Mar 2025 H1 U1 — No Details →
0.1.56 20 Feb 2025 H1 U1 — No Details →
0.1.55 06 Feb 2025 H1 U1 — No Details →
0.1.53 06 Feb 2025 H1 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for skyvern

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 skyvern

Is skyvern safe to use?

Vulert records 2 vulnerabilities for skyvern in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is skyvern's Vulert package health score?

Vulert scores skyvern 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 skyvern affected?

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

Which version of skyvern should I use?

1.0.56 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 skyvern have?

2 vulnerabilities are recorded for skyvern in the PyPI ecosystem: 0 critical, 1 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 skyvern vulnerabilities disclosed?

1 vulnerability was recorded for skyvern in the last 12 months, and the oldest entry in this database dates to 07 Jun 2025. 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 skyvern 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 skyvern for upcoming vulnerabilities?

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