OpenReception's logout page clears local access_token before server-side revocation, leaving duplicated tokens valid until expiry
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.2, when a user navigates to the `/logout` page, the page's server-side load handler deletes the `access_token` cookie before calling `/api/auth/logout` via an internal `event.fetch()`. The internal fetch consequently runs without the auth cookie, so `apiAuthHandle` rejects it, the logout handler never executes, and `SessionService.revokeSession()` is never called for the current session. The DB session row remains valid until its natural expiry (one week by default). The user sees a successful logout (cookie gone, UI returns to login), but any party still holding a copy of the now-deleted access token can continue making authenticated API calls until the session naturally expires. The root cause is a simple ordering mistake. The same auth subsystem implements the correct order in `/api/auth/logout`: revoke the current DB session first, then delete the cookie. The page-level wrapper does the opposite. Version 1.0.2 initiates server-side logout before removing authentication cookies and first appears in version 1.0.2. Version 2.0.0 later replaces this with a race-free client-side logout flow.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-48079
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 00:28 UTC · Revision 1
Source evidence
OpenReception's logout page clears local access_token before server-side revocation, leaving duplicated tokens valid until expiry
core-osv · Original sourcePublished 6 Aug 2026, 21:00 UTC
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.2, when a user navigates to the `/logout` page, the page's server-side load handler deletes the `access_token` cookie before calling `/api/auth/logout` via an internal `event.fetch()`. The internal fetch consequently runs without the auth cookie, so `apiAuthHandle` rejects it, the logout handler never executes, and `SessionService.revokeSession()` is never called for the current session. The DB session row remains valid until its natural expiry (one week by default). The user sees a successful logout (cookie gone, UI returns to login), but any party still holding a copy of the now-deleted access token can continue making authenticated API calls until the session naturally expires. The root cause is a simple ordering mistake. The same auth subsystem implements the correct order in `/api/auth/logout`: revoke the current DB session first, then delete the cookie. The page-level wrapper does the opposite. Version 1.0.2 initiates server-side logout before removing authentication cookies and first appears in version 1.0.2. Version 2.0.0 later replaces this with a race-free client-side logout flow.
osv:CVE-2026-48079
Complete source record
{
"id": "22b15bac1fdcd5e76c91f9917b8081183966cfd8e044835542bbf53df618bce2",
"url": "https://osv.dev/vulnerability/CVE-2026-48079",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "OpenReception's logout page clears local access_token before server-side revocation, leaving duplicated tokens valid until expiry",
"summary": "OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.2, when a user navigates to the `/logout` page, the page's server-side load handler deletes the `access_token` cookie before calling `/api/auth/logout` via an internal `event.fetch()`. The internal fetch consequently runs without the auth cookie, so `apiAuthHandle` rejects it, the logout handler never executes, and `SessionService.revokeSession()` is never called for the current session. The DB session row remains valid until its natural expiry (one week by default). The user sees a successful logout (cookie gone, UI returns to login), but any party still holding a copy of the now-deleted access token can continue making authenticated API calls until the session naturally expires. The root cause is a simple ordering mistake. The same auth subsystem implements the correct order in `/api/auth/logout`: revoke the current DB session first, then delete the cookie. The page-level wrapper does the opposite. Version 1.0.2 initiates server-side logout before removing authentication cookies and first appears in version 1.0.2. Version 2.0.0 later replaces this with a race-free client-side logout flow.",
"evidence": "osv:CVE-2026-48079",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-48079",
"aliases": [
"CVE-2026-48079",
"GHSA-hrhm-m2hm-7cjh"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/open-reception/appointment-booking-software",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "b283dbb670e09112299fb0cf89f3cb054ecc1700"
},
{
"fixed": "2419f9e87a8abad72f31b1fedeb80c758b30322e"
},
{
"fixed": "f833dbf50059ff7d4ea42ce7bbb3a5cdcf7a6929"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.0.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "2419f9e87a8abad72f31b1fedeb80c758b30322e"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "f833dbf50059ff7d4ea42ce7bbb3a5cdcf7a6929"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.0.1",
"v1.0.0",
"v1.0.0-rc2",
"v1.0.0-rc"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-48079.json"
}
}
],
"modified": "2026-10-28T02:30:52.142841740Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48079.json",
"https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-hrhm-m2hm-7cjh",
"https://nvd.nist.gov/vuln/detail/CVE-2026-48079",
"https://github.com/open-reception/appointment-booking-software/commit/2419f9e87a8abad72f31b1fedeb80c758b30322e",
"https://github.com/open-reception/appointment-booking-software/commit/f833dbf50059ff7d4ea42ce7bbb3a5cdcf7a6929"
],
"provider_metadata": {
"cwe_ids": [
"CWE-613"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48079.json"
}
},
"related_cves": [
{
"value": "CVE-2026-48079",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 520970,
"published_at": "2026-08-06T21:00:44.615+00:00"
}