Skip to content

SECURITY: CVE IDs come from the EEF CNA, which covers hex.pm, not from GitHub - #16

Merged
HackTuah merged 1 commit into
mainfrom
docs/cve-from-eef-cna
Oct 7, 2026
Merged

HackTuah merged 1 commit into
mainfrom
docs/cve-from-eef-cna

Conversation

@HackTuah

@HackTuah HackTuah commented Oct 7, 2026

Copy link
Copy Markdown
Member

GitHub does not assign a CVE for a package another CNA covers, and the Erlang Ecosystem Foundation's CNA covers every active hex.pm package, so the 0.2.1 request to GitHub could not be answered. The CVEs section now follows the EEF CNA's maintainer process (https://cna.erlef.org/maintainer-process).

…m GitHub

GitHub is a CNA but does not assign for a package another CNA covers, and the Erlang
Ecosystem Foundation's CNA covers every active package on hex.pm: 0.2.1's CVE request to
GitHub (2026-09-23) was never going to be answered. The section now gives the EEF CNA's
maintainer process (its points of contact as collaborators on the draft, the ID entered as
an existing CVE) and says what happened to 0.2.1's request.

Signed-off-by: Ayla Croft <aylacroft@proton.me>
@HackTuah
HackTuah force-pushed the docs/cve-from-eef-cna branch from a0e5f2b to d309ff2 Compare October 7, 2026 23:44
@HackTuah
HackTuah merged commit bb38084 into main Oct 7, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant