Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Path Traversal in Apache Atlas

CVE-2016-8752GHSA-m2rr-h6g4-9cm9

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI apache-atlas

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Maven org.apache.atlas:atlas-common

    Affected
    >= 0.6.0-incubating, < 0.8-incubating
    Fixed in
    0.8-incubating

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2016-8752: 2.13% estimated exploitation activity in the next 30 days; percentile 81.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Apache Atlas versions 0.6.0 (incubating), 0.7.0 (incubating), and 0.7.1 (incubating) allow access to the webapp directory contents by pointing to URIs like /js and /img.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-m2rr-h6g4-9cm9

  2. Revision 1 · created ·

    Published from osv record PYSEC-2017-105

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2016-8752

Advisory: Path Traversal in Apache Atlas
IDs: CVE-2016-8752, GHSA-m2rr-h6g4-9cm9
Record: https://patchnext.com/advisories/cve-2016-8752 (revision 2, source checked 26 Oct 2026, 16:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.apache.atlas:atlas-common 0.8-incubating. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI apache-atlas: affected every version
- Maven org.apache.atlas:atlas-common: affected >= 0.6.0-incubating, < 0.8-incubating; fixed in 0.8-incubating

## Suggested inspection (read-only)
- `python -m pip show apache-atlas`: prints the installed version. Run with the environment that serves production active.
- Maven org.apache.atlas:atlas-common: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on apache-atlas, org.apache.atlas:atlas-common.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/PYSEC-2017-105 (OSV record PYSEC-2017-105 lists affected ranges: PyPI apache-atlas >=0)
- Verified: https://github.com/advisories/GHSA-m2rr-h6g4-9cm9 (GitHub-reviewed advisory GHSA-m2rr-h6g4-9cm9 lists affected ranges: Maven org.apache.atlas:atlas-common >=0.6.0-incubating <0.8-incubating)

Commands are suggestions: review each one before running it.

Loading voting…