Narrative
Vulnerability disclosure program on security.txt narrative.io
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- 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
We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date.
- Safe harbor
-
Full
If you have followed the instructions above, we will not take any legal action against you in regard to the report.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 13 excluded.
Domains 1
- narrative.io
Out of scope (13)
- Any activity that could lead to disruption of our services (DoS)
- Attacks requiring physical access to the victim’s computer
- Clickjacking on pages with no sensitive actions
- CSRF without any security impact
- Internationalized domain name (IDN) homograph attacks
- Lack of Secure or HTTP only flag on non-sensitive cookies
- Man-in-middle attacks
- Missing DNSSEC, CAA, or CSP headers
- Reports about CVEs published on mailing lists, groups etc. without demonstrating an impact on Narrative
- Right-to-left (RTL) Ambiguity
- RTL Override (RTLO)
- Social engineering, phishing, or other fraud
- Tabnabbing
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Narrative's policy. "We" in these lines means the program, not this site.
While testing
-
Do not run automated scanners on our infrastructure or dashboard.
-
Do not exploit the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data.
-
Do not reveal the problem to others until it has been resolved.
-
Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties.
-
Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible.
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Man-in-middle attacks
-
Attacks requiring physical access to the victim’s computer
-
Social engineering, phishing, or other fraud
-
Internationalized domain name (IDN) homograph attacks
-
Right-to-left (RTL) Ambiguity
-
RTL Override (RTLO)
-
Tabnabbing
-
Any activity that could lead to disruption of our services (DoS)
-
Missing DNSSEC, CAA, or CSP headers
-
CSRF without any security impact
-
Lack of Secure or HTTP only flag on non-sensitive cookies
-
Reports about CVEs published on mailing lists, groups etc. without demonstrating an impact on Narrative
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 2 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.