nebula-mesh: POST /api/v1/hosts/{id}/mobile-bundle response lacks Cache-Control: no-store

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

internal/api/mobilebundle.go:62-66 sets only Content-Type: application/yaml. The Web-UI sibling at internal/web/handlers.go:1316-1321 sets Cache-Control: no-store, Pragma: no-cache, Expires: 0, X-Content-Type-Options: nosniff — and has a test asserting it. The API path was missed. Affected All released versions up to v0.3.0. Threat model The endpoint returns a freshly minted X25519 private key inline. Without no-store, any intermediary proxy or CDN that caches 200 OK YAML responses retains the private key for its cache TTL. Same applies to browser disk cache for direct API hits. Combined with the cross-tenant authz advisory (critical), even a corrected authz layer would still leak via cache after fix. Suggested fix Copy the four headers from the Web sibling: Mirrors internal/web/handlers.go:1316-1321. Add a parallel test to the existing web-side coverage. Suggested patch Verified locally: go vet, go test -race -count=1 ./..., golangci-lint v2.12 all clean.

Published by the source

12 Jun 2026, 18:30 UTC

Last modified by the source

12 Jun 2026, 18:30 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6vgg-xhvh-38ff

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-6vgg-xhvh-38ff

Advisory: nebula-mesh: POST /api/v1/hosts/{id}/mobile-bundle response lacks Cache-Control: no-store
IDs: GHSA-6vgg-xhvh-38ff
Record: https://patchnext.com/advisories/ghsa-6vgg-xhvh-38ff (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/juev/nebula-mesh 0.3.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/juev/nebula-mesh: affected <= 0.3.1; fixed in 0.3.2

## Suggested inspection (read-only)
- Go github.com/juev/nebula-mesh: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/juev/nebula-mesh.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6vgg-xhvh-38ff (GitHub-reviewed advisory GHSA-6vgg-xhvh-38ff lists affected ranges: Go github.com/juev/nebula-mesh >=0 <=0.3.1)

Commands are suggestions: review each one before running it.