GHSA-r7rh-jww5-5fjr is a medium-severity (CVSS 6.8) CWE-863 vulnerability in github.com/pomerium/pomerium. A fix is available for github.com/pomerium/pomerium — see the affected versions and patch details below.
Pomerium service account access token may grant unintended access to databroker API
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-r7rh-jww5-5fjr.
EPSS Exploitation Probability
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-r7rh-jww5-5fjr 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 377,166 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
github.com/pomerium/pomeriumReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
We've identified a vulnerability in the Pomerium databroker service API that may grant unintended access under specific conditions. This affects only certain Pomerium Zero and Pomerium Enterprise deployments.
Who is affected?
A Pomerium deployment is susceptible to this issue if all of the following conditions are met:
- You have issued a service account access token using Pomerium Zero or Pomerium Enterprise.
- The access token has an explicit expiration date in the future.
- The core Pomerium databroker gRPC API is not otherwise secured by network access controls.
If your deployment does not meet all of these conditions, you are not affected by this vulnerability.
Details
The Pomerium databroker service is responsible for managing all persistent Pomerium application state. Requests to the databroker service API are authorized by the presence of a JSON Web Token (JWT) signed by a key known by all Pomerium services in the same deployment. However, incomplete validation of this JWT meant that some service account access tokens would incorrectly be treated as valid for the purpose of databroker API authorization.
Improper access to the databroker API could allow exfiltration of user info, spoofing of user sessions, or tampering with Pomerium routes, policies, and other settings.
Discovery
This issue was discovered during internal review. At this time we have no evidence to suggest that this vulnerability has been exploited in the wild.
Patches
We have released Pomerium v0.27.1 which includes a fix for the JWT validation logic. All affected users are strongly encouraged to upgrade to this version.
Workarounds
If you cannot upgrade immediately, consider the following mitigations:
-
Network access controls: Restrict access to the Pomerium internal gRPC API by configuring your network firewall or security groups to limit access to trusted sources only. Ensure that the port specified in the
grpc_addresssetting is not exposed to unauthorized networks. -
For Pomerium Zero deployments only: As of Pomerium v0.26.0, you can disable the gRPC API listener by setting
grpc_address: ""in your YAML configuration file. In all-in-one mode, Pomerium does not require the internal gRPC API to be exposed beyond localhost.
For more information
If you have questions or need further assistance:
- Open an issue in the pomerium/pomerium repository.
- Contact us at [email protected].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/pomerium/pomerium | all versions | 0.27.1go get github.com/pomerium/pomerium@v0.27.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pomerium/pomerium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/pomerium/pomerium to 0.27.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7rh-jww5-5fjr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r7rh-jww5-5fjr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r7rh-jww5-5fjr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r7rh-jww5-5fjr in your dependencies?
O3 Security finds GHSA-r7rh-jww5-5fjr across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.