Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48154 medium CVSS 5.9

Vulnerability in github.com/pilinux/gorest (CVE-2026-48154)

Summary

Vulnerability in github.com/pilinux/gorest (CVE-2026-48154). Risk of unauthorized operations or information disclosure. Exploitable via InMemorySecret2FA. Mitigation: upgrade to 1.12.2 or later.

Original description

The description as published by the source.

Vulnerability: CWE-362 — Concurrent Map Access Race Condition in InMemorySecret2FA

CWE: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

Affected Component

  • github.com/pilinux/gorest — Go REST API boilerplate
  • InMemorySecret2FA — in-memory 2FA secret store

Vulnerability Locations

File Line Role
database/model/twoFA.go 43 Global map[uint64]Secret2FA — bare map, no sync.RWMutex
handler/login.go 139 Map write during user login
handler/twoFA.go 205 Map write during 2FA setup
handler/twoFA.go 272 Map write during 2FA activation
handler/twoFA.go 575 Map write during 2FA verification
handler/twoFA.go 189 Map read during 2FA operations
handler/twoFA.go 245 Map read during 2FA operations
handler/twoFA.go 491 Map read during 2FA operations
service/common.go 79 Map delete

Data Flow

Multiple HTTP goroutines (concurrent requests)
    │
    ├── handler/login.go:139 ─► map write ──┐
    ├── handler/twoFA.go:205 ─► map write ──┼── InMemorySecret2FA (bare map)
    ├── handler/twoFA.go:189 ─► map read ───┤      ▲  NO sync.RWMutex
    ├── handler/twoFA.go:245 ─► map read ───┤      │
    ├── handler/twoFA.go:491 ─► map read ───┤      │
    └── service/common.go:79 ─► map delete ─┘      │
                                                   │
            Go runtime detects concurrent map      │
            read+…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-48154 has been found in github.com/pilinux/gorest.
Attackers can target a specific entry point like InMemorySecret2FA over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.9/10.
What to do: upgrade github.com/pilinux/gorest to 1.12.2 or later.
If unsure, ask your IT team or search "github.com/pilinux/gorest CVE-2026-48154" on the vendor's site.

CVE-2026-48154 (github.com/pilinux/gorest) — CWE-362 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: InMemorySecret2FA / Secret2FAStore / sync.RWMutex
Patched: 1.12.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-362) exists in github.com/pilinux/gorest. Attackers reach the vulnerable code path via InMemorySecret2FA without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/pilinux/gorest. Attack surface: InMemorySecret2FA / Secret2FAStore / sync.RWMutex.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.12.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/pilinux/gorest' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/pilinux/gorest' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/pilinux/gorest を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/pilinux/gorest to 1.12.2

    ステージング環境で 1.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/pilinux/gorest
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.12.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details