Search results

Missing resolution version for PYSEC-2023-243

Status: Open.

#253 In pypa/advisory-database;

· zanieb opened on Dec 16, 2025

<code>PYSEC-2023-241</code> specifies vulnerable versions that are not actually vulnerable

Status: Open.

#251 In pypa/advisory-database;

· cswimr opened on Dec 10, 2025

Broken timestamp in a vulnerability record (except if we discovered it 2024 year ago 😉

Status: Open.

#247 In pypa/advisory-database;

· adulau opened on Sep 10, 2025

Draft issue: Additional information needed for create_advisory.sh generated advisories

Status: Open.

#243 In pypa/advisory-database;

· JevgenijsCipisevs777 opened on Jul 18, 2025

Enquiry on when withdrawn is used.

Status: Open.

#234 In pypa/advisory-database;

· petermcd opened on Apr 30, 2025

vulns/steam/PYSEC-2019-125.yaml is likely incorrect?

Status: Open.

#233 In pypa/advisory-database;

· pombredanne opened on Apr 29, 2025

Can build tags be supported as part of version ranges for fix present or not?

Status: Open.

#232 In pypa/advisory-database;

· xnox opened on Apr 29, 2025

Possible False positive PYSEC-2022-252

Status: Open.

#231 In pypa/advisory-database;

· raqsilva8 opened on Apr 23, 2025

Is 2025 data being used?

Status: Open.

#228 In pypa/advisory-database;

· andrewpollock opened on Mar 17, 2025

Missing Published Dates in Advisories

Status: Open.

#220 In pypa/advisory-database;

· gokul-sankars-22084 opened on Dec 11, 2024

Description for aiocpa entry is wrong

Status: Open.

#218 In pypa/advisory-database;

· malemburg opened on Dec 9, 2024

Possible false positive on pyQuEST: PYSEC-2022-43051

Status: Open.

#216 In pypa/advisory-database;

· isobelhooper opened on Nov 29, 2024