gorest InMemorySecret2FA race condition allows process crash via concurrent map access (CWE-362)

Exploitation

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

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-48154: 0.40% estimated exploitation activity in the next 30 days; percentile 34.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 Description The InMemorySecret2FA in database/model/twoFA.go was defined as a…

Published by the source

12 Jun 2026, 18:29 UTC

Last modified by the source

12 Jun 2026, 18:29 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cpwg-x64r-rgwg

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

# Patch Next advisory brief: CVE-2026-48154

Advisory: gorest InMemorySecret2FA race condition allows process crash via concurrent map access (CWE-362)
IDs: CVE-2026-48154, GHSA-cpwg-x64r-rgwg
Record: https://patchnext.com/advisories/cve-2026-48154 (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: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pilinux/gorest 1.12.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pilinux/gorest: affected <= 1.12.1; fixed in 1.12.2

## Suggested inspection (read-only)
- Go github.com/pilinux/gorest: 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/pilinux/gorest.
- 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-cpwg-x64r-rgwg (GitHub-reviewed advisory GHSA-cpwg-x64r-rgwg lists affected ranges: Go github.com/pilinux/gorest >=0 <=1.12.1)

Commands are suggestions: review each one before running it.