How severe is GHSA-q537-qhj4-wcjx?

GHSA-q537-qhj4-wcjx has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q537-qhj4-wcjx?

GHSA-q537-qhj4-wcjx affects the following packages: pycti (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-q537-qhj4-wcjx?

Update pycti to 6.9.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q537-qhj4-wcjx is resolved across your whole dependency graph.

How do I detect GHSA-q537-qhj4-wcjx in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pycti. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q537-qhj4-wcjx if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-q537-qhj4-wcjx?

O3 pinpoints whether GHSA-q537-qhj4-wcjx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q537-qhj4-wcjx actively exploited in the wild?

No public exploit code has been indexed for GHSA-q537-qhj4-wcjx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q537-qhj4-wcjx?

GHSA-q537-qhj4-wcjx has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q537-qhj4-wcjx?

GHSA-q537-qhj4-wcjx is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q537-qhj4-wcjx published, and has it been updated?

GHSA-q537-qhj4-wcjx was published on May 28, 2026 and was last updated on May 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-q537-qhj4-wcjx

HIGH

OpenCTI: Privilege escalation via graphQL API is abusable by organization admins, due to incorrect ACL on userEdit relationAdd

Also known asCVE-2026-44730PYSEC-2026-167

Published

May 28, 2026

Updated

May 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk24th percentile0.00%

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.

Blast Radius

1 pkg affected

🐍pycti

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

Summary

An organization admin can escalate their privileges by adding a user from a different organization with higher privileges, to their own organization.

Impact

Full platform access, access to sensitive or proprietary information.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pycti`	all versions	6.9.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pycti. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update pycti to 6.9.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q537-qhj4-wcjx is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-q537-qhj4-wcjx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q537-qhj4-wcjx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An organization admin can escalate their privileges by adding a user from a different organization with higher privileges, to their own organization. ### Impact Full platform access, access to sensitive or proprietary information.

O3 Security · Impact-Aware SCA

Is GHSA-q537-qhj4-wcjx in your dependencies?

O3 detects GHSA-q537-qhj4-wcjx across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works