Repository advisory GHSA-c7vj-4cqh-8cv9 not available in the GitHub Advisory Database

Open
#9,435 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
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
security

Research direction

Review the linked repository advisory for GHSA-c7vj-4cqh-8cv9 and the global advisory URL, then determine the GitHub Advisory Database eligibility and ingestion path. Done means the advisory is available globally or the issue receives a clear explanation of why it is not eligible.

Written by the indexing model from the issue text.

Description

Summary

The published repository security advisory GHSA-c7vj-4cqh-8cv9 for wollomatic/socket-proxy is not currently available through the global
GitHub Advisory Database.

The advisory is published in the source repository:

However, the corresponding global advisory URL returns HTTP 404:

Advisory details

  • GHSA: GHSA-c7vj-4cqh-8cv9
  • Repository: wollomatic/socket-proxy
  • Package: github.com/wollomatic/socket-proxy
  • Ecosystem: Go
  • Severity: Critical
  • CVSS: 9.6
  • Affected versions: >= 1.8.0, <= 1.12.3
  • Patched version: 1.13.0
  • Published: 2026-08-13
  • CVE: No known CVE

The repository advisory describes a restriction bypass in the -allowbindmountfrom / SP_ALLOWBINDMOUNTFROM control. Under affected
configurations, a client may be able to create Docker containers, Swarm services, or volumes with host bind mounts outside the configured
allowlist.

Request

Could you please review the advisory and either:

  1. ingest it into the global GitHub Advisory Database, or
  2. provide information about why it is not eligible for ingestion?

A CVE was already requested through GitHub's "Request CVE" workflow some time ago. However, no CVE has been assigned so far, and the advisory
is still not available through the global GitHub Advisory Database (see also https://github.com/wollomatic/socket-proxy/issues/176).

Thank you.

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

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 Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.