Request a CVE ID for published advisory GHSA-pcc4-rvhr-2pr8
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 8/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- security
Research direction
No repository files, tests or entry points are involved; the work happens in GitHub's security advisory UI for GHSA-pcc4-rvhr-2pr8, which only a maintainer can use. Done means a CVE is assigned to the advisory and the requested credit is added. A newcomer cannot complete this, and the MITRE and CVE-assignment question is still being settled by the requester.
Written by the indexing model from the issue text.
Description
Hi, thanks for fixing and publishing this advisory (fixed in 0.9.70):
It doesn't have a CVE ID yet. Could you open the advisory and click "Request CVE"? GitHub then assigns one, and scanners like Dependabot and OSV flag the affected versions so users know to upgrade.
Could you also add @aaronjmars as a credit (type: finder)? I run @aeonframework, the Aeon security agent that found this, so both accounts should be on it.
I also asked MITRE for a CVE on 2026-09-28 but have had no reply. GitHub is usually much faster. Whichever assigns first, I'll withdraw the other so there's only one CVE.
Thanks!
Aaron Elijah Mars, Aeon (https://www.aeon.fun)
- Dominant language
- Python
- Stars
- 124k
- Forks
- 11.9k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Graphify-Labs/graphify
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Graphify-Labs/graphify#3763 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Graphify-Labs/graphify#3611 · 1 comment ·
Maintainers usually reply within 1 day
-
Nix supportOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Graphify-Labs/graphify#3193 · 2 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Graphify-Labs/graphify#2871 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Graphify-Labs/graphify#2865 ·
Maintainers usually reply within 1 day
All issues in Graphify-Labs/graphify
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
topoteretes/cognee#5773 ·
Maintainers usually reply within 1 day
-
MiKTeX: a failed build reports no errors because texify --quiet switches the log to file:line: styleOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
SublimeText/LaTeXTools#1718 ·