Splunk images still ship Node.js from before the 21 Oct 2026 security releases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 54/100
Research direction
Start by checking how the repository builds and publishes the splunk/splunk image tags, then locate where the Node.js runtime version is selected. Update the image to use one of the patched Node.js versions listed in the issue and verify the built image with node -v; done when a published tag reports a patched version.
Written by the indexing model from the issue text.
Description
Splunk Enterprise images still include a Node.js runtime older than the 21 October 2026 security releases.
The patched minimums on supported Node.js lines are 22.23.4, 24.22.1, and 26.12.1. Node.js 20 received no backport.
What we are running:
- Image line
splunk/splunk:10.0.5 node -vinside that image reportsv20.19.4
The newest public tag, splunk/splunk:10.6.1, was published on 20 October 2026, the day before those Node.js releases, so it cannot contain 22.23.4, 24.22.1, or 26.12.1 either.
Please publish a splunk/splunk tag whose node -v is v22.23.4, v24.22.1, or v26.12.1.
Node.js advisory: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
- Dominant language
- Python
- Stars
- 555
- Forks
- 278
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 splunk/docker-splunk
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
splunk/docker-splunk#730 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
splunk/docker-splunk#738 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
splunk/docker-splunk#737 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
splunk/docker-splunk#732 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
splunk/docker-splunk#731 · 1 reaction ·
All issues in splunk/docker-splunk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
roman-corgi/corgisim#327 ·
Maintainers usually reply within 2 days
-
[Bug]: opencode_go chat route drops reasoning_effort (even 'none'), while the same endpoint honors it via custom_llm_provider=openaiPossibly taken @arvindkumar-ship-it claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
BerriAI/litellm#51871 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
PolicyEngine backdates South Carolina’s EITC into 2015–2017Possibly taken @MaxGhenis claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/policyengine-us#10944 ·
Maintainers usually reply within 2 days
-
fix(frontend): resolve SSE parser crash on unhandled Ref methods and undefined actions identifierOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kodokbakar/MiroFish-Local#94 ·
Maintainers usually reply within 1 day