Vulnerability Database · PyPI · Package report

structlog: vulnerability history, versions and safety

Q: How do I monitor structlog for upcoming vulnerabilities?

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

structlog is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all structlog vulnerabilities

Vulert verdict on structlog 26.1.0 i

Updated on 23 Oct 2026

Good news: 26.1.0, the version you would install today, has no known vulnerabilities.

Package health score 87/100

Security No known security issues
Maintenance Sustainable
Popularity Key ecosystem project
Community Moderate

What to do: Stay on 26.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 26.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release 26.1.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 4,720 packages i
Stars 4,980 i
OpenSSF scorecard 7/10 i
Last release 4 months ago i
Licence Apache-2.0 OR MIT 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for structlog, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
26.1.0	06 Jun 2026	none	Apache-2.0 OR MIT	—	Details →
25.5.0	27 Oct 2025	none	Apache-2.0 OR MIT	—	Details →
25.4.0	02 Jun 2025	none	Apache-2.0 OR MIT	—	Details →
25.3.0	25 Apr 2025	none	Apache-2.0 OR MIT	—	Details →
25.2.0	11 Mar 2025	none	Apache-2.0 OR MIT	—	Details →
25.1.0	16 Jan 2025	none	Apache-2.0 OR MIT	—	Details →
24.4.0	17 Jul 2024	none	Apache-2.0 OR MIT	—	Details →
24.3.0	17 Jul 2024	none	Apache-2.0 OR MIT	—	Details →
24.2.0	27 May 2024	none	Apache-2.0 OR MIT	—	Details →
24.1.0	08 Jan 2024	none	Apache-2.0 OR MIT	—	Details →
23.3.0	29 Dec 2023	none	Apache-2.0 OR MIT	—	Details →
23.2.0	09 Oct 2023	none	Apache-2.0 OR MIT	—	Details →
23.1.0	06 Apr 2023	none	non-standard	—	Details →
22.3.0	24 Nov 2022	none	non-standard	—	Details →
22.2.0	19 Nov 2022	none	non-standard	—	Details →
22.1.0	20 Jul 2022	none	non-standard	—	Details →
21.5.0	16 Dec 2021	none	non-standard	—	Details →
21.4.0	25 Nov 2021	none	non-standard	—	Details →
21.3.0	20 Nov 2021	none	non-standard	—	Details →
21.2.0	12 Oct 2021	none	non-standard	—	Details →
21.1.0	18 Feb 2021	none	non-standard	—	Details →
20.2.0	31 Dec 2020	none	non-standard	—	Details →
20.1.0	28 Jan 2020	none	non-standard	—	Details →
19.2.0	16 Oct 2019	none	non-standard	—	Details →
19.1.0	02 Feb 2019	none	non-standard	—	Details →
18.2.0	05 Sep 2018	none	non-standard	—	Details →
18.1.0	27 Jan 2018	none	non-standard	—	Details →
17.2.0	15 May 2017	none	non-standard	—	Details →
17.1.0	24 Apr 2017	none	non-standard	—	Details →
16.1.0	24 May 2016	none	non-standard	—	Details →
16.0.0	28 Jan 2016	none	non-standard	—	Details →
15.3.0	25 Sep 2015	none	non-standard	—	Details →
15.2.0	10 Jun 2015	none	non-standard	—	Details →
15.1.0	24 Feb 2015	none	non-standard	—	Details →
15.0.0	23 Jan 2015	none	non-standard	—	Details →
0.4.2	26 Jul 2014	none	Apache-2.0	—	Details →
0.4.1	19 Dec 2013	none	Apache-2.0	—	Details →
0.4.0	10 Nov 2013	none	Apache-2.0	—	Details →
0.3.2	27 Sep 2013	none	Apache-2.0	—	Details →
0.3.1	26 Sep 2013	none	Apache-2.0	—	Details →
0.3.0	23 Sep 2013	none	Apache-2.0	—	Details →
0.2.0	17 Sep 2013	none	Apache-2.0	—	Details →
0.1.0	12 Sep 2013	none	Apache-2.0	—	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for structlog

No vulnerabilities match this view.

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 structlog

Is structlog safe to use?

Vulert has no vulnerabilities on record for structlog in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is structlog's Vulert package health score?

Vulert scores structlog 87/100, which reads as healthy. 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 structlog affected?

No. 26.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of structlog should I use?

26.1.0 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 structlog have?

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

0 vulnerabilities were recorded for structlog in the last 12 months. 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 structlog 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 structlog for upcoming vulnerabilities?

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