Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-8xv7-89vj-q48c — accesscontrol

MEDIUMFix: zopefoundation/AccessControl@6bc3269

GHSA-8xv7-89vj-q48c is a medium-severity (CVSS 6.8) Information Exposure vulnerability in accesscontrol. A fix is available for accesscontrol — see the affected versions and patch details below.

Information disclosure in AccessControl

Also known asCVE-2023-41050PYSEC-2026-2075PYSEC-2026-2325
Published
Sep 7, 2023
Updated
Jul 13, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8xv7-89vj-q48c.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-8xv7-89vj-q48c plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

5 pkgs affected
🐍accesscontrol🐍zope🐍accesscontrol🐍accesscontrol🐍zope

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Python's "format" functionality allows someone controlling the format string to "read" objects accessible (recursively) via attribute access and subscription from accessible objects. Those attribute accesses and subscriptions use Python's full blown getattr and getitem, not the policy restricted AccessControl variants _getattr_ and _getitem_. This can lead to critical information disclosure.

AccessControl already provides a safe variant for str.format and denies access to string.Formatter. However, str.format_map is still unsafe.

Affected are all users who allow untrusted users to create AccessControl controlled Python code and execute it.

Patches

A fix will be introduced in the versions 4.4, 5.8 and 6.2.

Workarounds

There are no workarounds.

References

https://github.com/zopefoundation/RestrictedPython/security/advisories/GHSA-xjw2-6jm9-rf67 describes the corresponding problem for RestrictedPython.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIaccesscontrolall versions4.4pip install --upgrade 'accesscontrol==4.4'
🐍PyPIzopeall versions4.8.9pip install --upgrade 'zope==4.8.9'
🐍PyPIaccesscontrol≥ 5.0&&< 5.85.8pip install --upgrade 'accesscontrol==5.8'
🐍PyPIaccesscontrol≥ 6.0&&< 6.26.2pip install --upgrade 'accesscontrol==6.2'
🐍PyPIzope≥ 5.0.0&&< 5.8.45.8.4pip install --upgrade 'zope==5.8.4'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for accesscontrol, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update accesscontrol to 4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8xv7-89vj-q48c is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8xv7-89vj-q48c can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8xv7-89vj-q48c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Python's "format" functionality allows someone controlling the format string to "read" objects accessible (recursively) via attribute access and subscription from accessible objects. Those attribute accesses and subscriptions use Python's full blown `getattr` and `getitem`, not the policy restricted `AccessControl` variants `_getattr_` and `_getitem_`. This can lead to critical information disclosure. `AccessControl` already provides a safe variant for `str.format` and denies access to `string.Formatter`. However, `str.format_map` is still unsafe. Affected are all users who allow
O3 Security · Impact-Aware SCA

Is GHSA-8xv7-89vj-q48c in your dependencies?

O3 Security finds GHSA-8xv7-89vj-q48c across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-8xv7-89vj-q48c: Medium 6.8 severity | O3 Security