VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

peppol-py: vulnerability history, versions and safety

peppol-py is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 2 releases, from Nov 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 M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 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.

See all peppol-py vulnerabilities

Vulert verdict on peppol-py 1.2.5 i

Updated on 23 Oct 2026

Good news: 1.2.5, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 68/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 1.2.5 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.0 i
  • With no published fix 0 i
  • Stars 10 i
  • Last release this month i
  • Licence 0BSD 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 peppol-py, 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.2.5 19 Oct 2026 none 0BSD — Details →
1.2.4 11 Jun 2026 none 0BSD — Details →
1.2.3 21 Apr 2026 none 0BSD — Details →
1.2.2 07 Apr 2026 none 0BSD — Details →
1.2.1 24 Mar 2026 none 0BSD — Details →
1.2.0 19 Mar 2026 none 0BSD — Details →
1.1.5 10 Mar 2026 none 0BSD — Details →
1.1.4 04 Mar 2026 none 0BSD — Details →
1.1.3 27 Feb 2026 none 0BSD — Details →
1.1.2 09 Dec 2025 none 0BSD — Details →
1.1.1 13 Nov 2025 none 0BSD — Details →
1.1.0 07 Oct 2025 M1 U1 0BSD Yes Details →
1.0.0 26 Sep 2025 M1 U1 0BSD Yes Details →

All 13 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. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for peppol-py

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-66371: Peppol-py Vulnerable to XXE Attacks Due to Saxon Configuration 5.0 medium 1.1.1 28 Nov 2025
CVE-2025-66371: Peppol-py Vulnerable to XXE Attacks Due to Saxon Configuration 5.0 medium 1.1.1 07 Jul 2026

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 peppol-py

Is peppol-py safe to use?

Vulert records 2 vulnerabilities for peppol-py in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 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.

What is peppol-py's Vulert package health score?

Vulert scores peppol-py 68/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).

Is the latest version of peppol-py affected?

No. 1.2.5, 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.

How many vulnerabilities does peppol-py have?

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

2 vulnerabilities were recorded for peppol-py in the last 12 months, and the oldest entry in this database dates to 28 Nov 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 peppol-py 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 peppol-py for upcoming vulnerabilities?

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