Saxo Bank
Vulnerability disclosure program on Self-hosted home.saxo
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 7
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Response
-
Within 3 days
Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission)
- Safe harbor
-
Full
Not pursue or support any legal action related to your research related to the reporting of such issue
- Hall of fame
-
Yes
Your name/handle and a link for recognition in our Hall of Fame.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
7 assets you may test, 10 excluded.
Domains 3
- developer.saxo
- home.saxo
- www.home.saxo
APIs 1
- Simulation SaxoOpenAPI, directly or through www.developer.saxo
Products and areas 3
- Simulation SaxoInvestor
- Simulation SaxoTrader No bounty
- Simulation SaxoTrader for web, mobile, and desktop
Out of scope (10)
- Any services hosted by 3rd party providers and services
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Form spamming
- Missing cookie flags and security headers
- Network level Denial of Service (DoS/DDoS) vulnerabilities
- News feeds
- Price feeds
- UI and UX bugs and spelling mistakes
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Saxo Bank's policy. "We" in these lines means the program, not this site.
While testing
-
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security analysis
-
Perform analysis only within the scope set out below
-
Use exploits only to the extent necessary to confirm the presence of a vulnerability and once established, do not abuse the vulnerability further
-
Do not exfiltrate data, establish command line access and/or persistence, or pivot to other systems
-
Use the defined communication channels (as identified below) to report vulnerability information to us
-
Keep information about any suspected or confirmed security issues you’ve discovered confidential between yourself and Saxo Bank until we’ve had 90 days to resolve the issue
Not accepted
-
UI and UX bugs and spelling mistakes
-
Network level Denial of Service (DoS/DDoS) vulnerabilities
-
Missing cookie flags and security headers
-
Form spamming
-
Findings derived primarily from social engineering (e.g. phishing, vishing)
-
Findings from physical testing such as office access (e.g. open doors, tailgating)
-
Personally identifiable information (PII)
-
Financial data (such as credit card or bank account numbers)
-
Results from automated scanning tools
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.