VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

apache-atlas: vulnerability history, versions and safety

apache-atlas is a package in the PyPI ecosystem. Vulert records 7 vulnerabilities for it across 11 releases, first recorded in Aug 2017. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded U7
i
7 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 apache-atlas vulnerabilities

Vulert verdict on apache-atlas 0.0.16 i

Updated on 23 Oct 2026

Careful: 0.0.16 has 7 known vulnerabilities, and 7 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

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 0.0.16 — affected i
  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 29 Aug 2017 i
  • Highest CVSS 7.5 i
  • With no published fix 7 i
  • Stars 2,155 i
  • OpenSSF scorecard 4/10 i
  • Last release 23 months ago i
  • Licence Apache-2.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 apache-atlas, 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
0.0.16 22 Nov 2024 U7 Apache-2.0 No Details →
0.0.15 01 Dec 2023 U7 Apache-2.0 No Details →
0.0.14 05 Jun 2023 U7 Apache-2.0 No Details →
0.0.13 28 Feb 2023 U7 Apache-2.0 No Details →
0.0.12 08 Nov 2022 U7 Apache-2.0 No Details →
0.0.11 15 Mar 2021 U7 Apache-2.0 No Details →
0.0.5 14 Mar 2021 U7 Apache-2.0 No Details →
0.0.4 18 Jan 2021 U7 Apache-2.0 No Details →
0.0.3 15 Dec 2020 U7 Apache-2.0 No Details →
0.0.2 12 Dec 2020 U7 Apache-2.0 No Details →
0.0.1 04 Dec 2020 U7 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 7

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

03 Vulnerabilities

Recorded vulnerabilities for apache-atlas

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-8752: Apache Atlas Directory Traversal Vulnerability 7.5 high No fix published 29 Aug 2017
CVE-2017-3154: Apache Atlas - Excessive Information Exposure 7.5 high No fix published 29 Aug 2017
CVE-2017-3150: Apache Atlas - Accessible Cookies 6.1 medium No fix published 29 Aug 2017
CVE-2017-3151: Stored Cross-Site Scripting in Apache Atlas 6.1 medium No fix published 29 Aug 2017
CVE-2017-3152: Apache Atlas DOM XSS Vulnerability 6.1 medium No fix published 29 Aug 2017

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 apache-atlas

Is apache-atlas safe to use?

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

What is apache-atlas's Vulert package health score?

Vulert scores apache-atlas 50/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 apache-atlas affected?

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

Which version of apache-atlas should I use?

0.0.16 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 apache-atlas have?

7 vulnerabilities are recorded for apache-atlas in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 7 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 apache-atlas vulnerabilities disclosed?

0 vulnerabilities were recorded for apache-atlas in the last 12 months, and the oldest entry in this database dates to 29 Aug 2017. 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 apache-atlas 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 apache-atlas for upcoming vulnerabilities?

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