Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Promote published repository advisory GHSA-r2pf-9cw4-5j65 to Global Database (CVE-2026-68904)

Closed
#9,392 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
database, security

Research direction

Start with the repository advisory URL and compare its published status, CVE metadata, affected packages, patched version, and reporter credit with the request. Confirm the advisory is ingested into the Global Advisory Database with GitHub-Reviewed status, synchronized CVE metadata, and preserved reporter attribution.

Written by the indexing model from the issue text.

Description

Advisory Information
  • Repository Advisory URL: https://github.com/node-opcua/node-opcua/security/advisories/GHSA-r2pf-9cw4-5j65
  • Advisory ID: GHSA-r2pf-9cw4-5j65
  • CVE ID: CVE-2026-68904
  • Ecosystem: npm
  • Affected Packages:
    • node-opcua
    • node-opcua-client
    • node-opcua-transport
  • Affected Versions: >= 2.0.0, < 2.170.0
  • Patched Versions: 2.170.0
  • CWE: CWE-400 (Uncontrolled Resource Consumption)
  • CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Credits
  • Reporter / Finder: @Velluso (Credit has already been formally accepted on the repository advisory)
  • Remediation Developer: @erossignon
Details

The repository advisory has been published by the maintainer (@erossignon) and patched since version 2.170.0, with the CVE ID (CVE-2026-68904) already assigned on the repository draft. However, it has not yet been ingested into the Global Advisory Database (GitHub-Reviewed).

Could you please review and promote this advisory to the Global Database so that:

  1. It receives GitHub-Reviewed status.
  2. The CVE metadata is synced properly.
  3. The reporter credit (@Velluso) is preserved and mapped to the user profile?

Thank you!

Dominant language
No language data
Stars
2.5k
Forks
772
Avg merge
3d 15h
Merged PRs (30d)
46

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/advisory-database

All issues in github/advisory-database

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.