- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 2
- 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
- https://spring.io/security-policy
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
Scope
2 assets you may test.
Domains 1
- spring.io
Source code 1
- any project within the Spring portfolio (this includes projects in other GitHub organizations, such as Spring Cloud)
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Spring's policy.
While testing
-
Any potential security vulnerabilities should be reported through the Security Advisories page.
-
The Spring team needs to receive reports of potential security vulnerabilities through GitHub’s ability to privately report a security vulnerability .
Summarised with AI from the company's policy, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 3 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.