Skip to content

Conversation

@Dedal0
Copy link

@Dedal0 Dedal0 commented Nov 4, 2025

Added a security policy document outlining supported versions and vulnerability reporting, so vulnerabilities can be reported.

Description

Important Info

Blockers

Testing

New tests

Testing Performed

Testing Environment

Documentation

Notes for Reviewers

Added a security policy document outlining supported versions and vulnerability reporting, so vulnerabilities can be reported.
@Dedal0
Copy link
Author

Dedal0 commented Nov 14, 2025

Hello,

I've tried to contact to contact security team to report a security issue but no answer when sent to the email address security[[at]]payara[d0t]fish.

Please confirm the actual process.

@Pandrex247 Pandrex247 added the PR: Awaiting CLA Contributor does not have a CLA or has submitted an unconfirmed CLA. label Nov 20, 2025
@Pandrex247
Copy link
Member

@RamyaBill @deetewari @MeroRai FYI as you'll know the process better than I

@Dedal0
Copy link
Author

Dedal0 commented Dec 2, 2025

38 days since my first contact mail to security at payara dot fish. Is that the correct email address? The report includes all details about the vulnerability. Please confirm... The impact is relevant.

@MeroRai
Copy link
Member

MeroRai commented Dec 5, 2025

@Dedal0, thank you for your report. You can find our current policies on how Payara handles security issues here: https://docs.payara.fish/community/docs/Security/Overview.html. As outlined there, the correct process is to email any identified flaws or vulnerabilities to security@payara.fish. You’ve already done that, and our team is currently reviewing your submission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR: Awaiting CLA Contributor does not have a CLA or has submitted an unconfirmed CLA.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants