How severe is GHSA-pgh9-49q4-hqcx?

No CVSS score has been assigned to GHSA-pgh9-49q4-hqcx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pgh9-49q4-hqcx?

Affected package information for GHSA-pgh9-49q4-hqcx is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-pgh9-49q4-hqcx?

Upgrade the affected component to the fixed release for GHSA-pgh9-49q4-hqcx, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-pgh9-49q4-hqcx in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-pgh9-49q4-hqcx if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-pgh9-49q4-hqcx actively exploited in the wild?

No public exploit code has been indexed for GHSA-pgh9-49q4-hqcx 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-pgh9-49q4-hqcx?

GHSA-pgh9-49q4-hqcx has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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-pgh9-49q4-hqcx?

GHSA-pgh9-49q4-hqcx is classified as Improper Privilege Management (CWE-269). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pgh9-49q4-hqcx published, and has it been updated?

GHSA-pgh9-49q4-hqcx was published on November 3, 2026 and was last updated on November 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

SurrealDB 3.1.0 before 3.3.0 MCP Session Hijack via…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

SurrealDB from 3.1.0 before 3.3.0 contains an improper authentication vulnerability where the MCP BoundSubject fingerprint uses the access method name instead of per-user identity for JWT/Bearer access. Attackers with a valid low-privilege token for the same access method and a victim's mcp-session-id can hijack the session and execute MCP tools with the victim's roles and permissions.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-pgh9-49q4-hqcx, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

SurrealDB from 3.1.0 before 3.3.0 contains an improper authentication vulnerability where the MCP BoundSubject fingerprint uses the access method name instead of per-user identity for JWT/Bearer access. Attackers with a valid low-privilege token for the same access method and a victim's mcp-session-id can hijack the session and execute MCP tools with the victim's roles and permissions.

O3 Security · Impact-Aware SCA

Is GHSA-pgh9-49q4-hqcx in your dependencies?

Find it across your dependency tree, including transitive dependencies.

Scan my dependencies How O3 SCA works

SurrealDB 3.1.0 before 3.3.0 MCP Session Hijack via BoundSubject CollisionGHSA-pgh9-49q4-hqcx

EPSS Exploitation Probability

Description

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-pgh9-49q4-hqcx in your dependencies?