bbs-go through 4.4.6 contains a permission bypass vulnerability in the AdminMiddleware authorization logic where the read-only dashboard.user.view permission rule matches the /api/admin/user/synccount endpoint before the intended dashboard.user.update rule. Authenticated users with only view permissions can call the synccount endpoint to trigger expensive full-table user recounts and cache invalidations, causing denial of service through repeated concurrent database operations.
CVE-2026-103396
MEDIUMPre-NVD 4.34.3—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 4.3 from GitHub Security Advisory published 2026-09-30. A secondary CVSS source baseline 4.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: None knownExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3MEDIUMhigh confidence
- EG Risk
- 24EG Risk 24/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 19th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 30, 2026
Last Modified
September 30, 2026
Advisory Details (6)
Auto-updated Sep 30, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
bbs-go through 4.4.6 Incorrect Authorization via /api/admin/user/synccount | Advisories | VulnCheck
https://www.vulncheck.com/advisories/bbs-go-through-4.4.6-incorrect-authorization-via-api-admin-user-synccountgeneric
GitHub - mlogclub/bbs-go: A lightweight community and Q&A platform for forums, knowledge bases, and discussions.一个轻量级社区和问答平台。 · GitHub
https://github.com/mlogclub/bbs-gogeneric
bbs-go/internal/handlers/admin/user_handlers.go at v4.4.6 · mlogclub/bbs-go · GitHub
https://github.com/mlogclub/bbs-go/blob/v4.4.6/internal/handlers/admin/user_handlers.go#L47-L59generic
bbs-go/internal/permissions/admin_permission_registry.go at v4.4.6 · mlogclub/bbs-go · GitHub
https://github.com/mlogclub/bbs-go/blob/v4.4.6/internal/permissions/admin_permission_registry.go#L59-L60github_commit
commit 97d0bb3dcbac (mlogclub/bbs-go)
Fix landed in mlogclub/bbs-go commit 97d0bb3dcbac — awaiting tagged release
https://github.com/mlogclub/bbs-go/commit/97d0bb3dcbacd686fd5300295afbf4f4a5da7609generic
Admin permission rule ordering lets a view-only role trigger a full user-table recompute · Issue #303 · mlogclub/bbs-go · GitHub
https://github.com/mlogclub/bbs-go/issues/303Vendor Advisories for CVE-2026-103396(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-03 18:19 UTCEG score recompute
- 2026-10-03 18:19 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 18:06 UTCEG score recompute
- 2026-10-02 18:06 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 17:56 UTCGHSA enrichment
- 2026-09-30 17:45 UTCGHSA enrichment
- 2026-09-30 17:25 UTCGHSA enrichment
- 2026-09-30 15:37 UTCEG score recompute
- 2026-09-30 15:37 UTCGHSA enrichment
- 2026-09-30 14:52 UTCEG score recompute
- 2026-09-30 14:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-103396?
CVE-2026-103396 is a medium vulnerability published on September 30, 2026. bbs-go through 4.4.6 contains a permission bypass vulnerability in the AdminMiddleware authorization logic where the read-only dashboard.user.view permission rule matches the /api/admin/user/synccount endpoint before the intended dashboard.user.update rule. Authenticated users with only view…
When was CVE-2026-103396 disclosed?
CVE-2026-103396 was first published on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103396 actively exploited?
CVE-2026-103396 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103396?
CVE-2026-103396 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103396?
An upstream fix for CVE-2026-103396 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-103396 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-103396
Is Your Infrastructure Affected by CVE-2026-103396?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.