critical

CVE

CVE-2026-126187, CVE-2026-125120, CVE-2026-125119, CVE-2026-125117, CVE-2026-125116, CVE-2026-125118, CVE-2026-126539, CVE-2026-64682, CVE-2026-64670, CVE-2026-64671, CVE-2026-63660, CVE-2026-126066, CVE-2026-107372, CVE-2026-108167, CVE-2026-126128, CVE-2026-126129

CWE

CWE-94, CWE-943, CWE-1321, CWE-863, CWE-798, CWE-79, CWE-190, CWE-787

Affected Surface

  • npm `react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` versions `>= 19.0.0, < 19.0.9`, `>= 19.1.0, < 19.1.10`, `>= 19.2.0, < 19.2.9`, and `19.3.0` (`CVE-2026-126187` / `GHSA-xqc2-xf4c-x3h3`, CVSS v4.0 9.5 Critical, fixed in `19.0.9`, `19.1.10`, `19.2.9`, and `19.3.1`)
  • npm `mongoose` versions `< 6.13.12`, `>= 7.0.0, < 7.8.13`, `>= 8.0.0, < 8.24.7`, and `>= 9.0.0, < 9.11.4` (`CVE-2026-125120` / `GHSA-pcrw-h46h-c93h` CVSS 9.8 Critical fixed in `6.13.11` / `7.8.12` / `8.24.3` / `9.9.2`; `CVE-2026-125119` / `GHSA-gg4r-jv3p-qx3c` CVSS 7.5 High, `CVE-2026-125117` / `GHSA-8332-j7wj-wjw4` CVSS 8.2 High, `CVE-2026-125116` / `GHSA-wr5m-5jph-8m96`, and `CVE-2026-125118` / `GHSA-6972-9mcm-vhwj` fixed in `6.13.12` / `7.8.13` / `8.24.7` / `9.11.4`)
  • Self-hosted and cloud deployments of Directus (`directus` / `@directus/api`) versions `< 12.1.0` with WebSockets enabled in `public` auth mode (`CVE-2026-126539` / `GHSA-97xr-jchp-xm3c`, CVSS v4.0 9.2 Critical / v3.1 8.1 High, fixed in `12.1.0`)
  • Astro CMS `astro-blocks` `< 3.4.0` (`CVE-2026-64682` / `GHSA-mfcg-m7j5-7v72`, CVSS 9.8 Critical), npm `@waline/client` `<= 3.15.2` (`CVE-2026-64670` / `GHSA-crj3-q72p-ggqm` CVSS 9.3 Critical and `CVE-2026-64671` CVSS 7.2 High), Mapbox `fontnik` (`node-fontnik`) `< 0.7.7` (`CVE-2026-63660` / `GHSA-cfm6-c7rv-58xj`, CVSS 8.1 High), `fast-xml-parser` `<= 5.11.2` (`CVE-2026-126066` / `GHSA-474x-hrwr-fgx4`, fixed in `5.12.0`), and Auth0 RAG / Management SDKs (`auth0-ai-js` `CVE-2026-107372`, `auth0-ai-python` `CVE-2026-108167`, `auth0` Node.js SDK `CVE-2026-126128`, and `Auth0.AspNetCore.Authentication` `CVE-2026-126129`)

TL;DR

Between 19:37 UTC on 10 November and 05:19 UTC on 11 November 2026, NVD, the GitHub Advisory Database, and upstream maintainers disclosed 16 vulnerabilities across React Server Components, Mongoose, Directus, AstroBlocks, Waline, Mapbox node-fontnik, fast-xml-parser, and Auth0’s AI and authentication SDKs:

  1. React Server Components 19.0.9, 19.1.10, 19.2.9, and 19.3.1 unauthenticated RCE (CVE-2026-126187 / GHSA-xqc2-xf4c-x3h3, CVSS v4.0 9.5 Critical): Affects react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack across all 19.x release lines (19.0.0 to 19.0.8, 19.1.0 to 19.1.9, 19.2.0 to 19.2.8, and 19.3.0). When a Flight stream serializes multiple typed arrays sharing an ArrayBuffer larger than VIEW_SIZE (4,096 bytes), transferring the first buffer-spanning view to a readable byte stream detaches the underlying ArrayBuffer (byteLength === 0). When the second view was written, writeChunk / writeViewChunk saw chunk.byteLength === 0 and returned early after the Flight framing header had already declared the original byte length, shifting the stream framing so subsequent attacker-controlled bytes in the response were decoded as Flight model and server-reference chunks. Commit 0c9913ae8728 also hides ResolvedModelChunk.reason behind an unforgeable Symbol() (RESPONSE_SYMBOL), blocks key === 'then' and non-ReactPromise metaData.bound values in loadServerReference(), and isolates string, stream (prefix + 'S' + id), and Blob entries in ReactFlightReplyBackingFormData.js.
  2. Mongoose 6.13.12, 7.8.13, 8.24.7, and 9.11.4 patch five query-injection and inherited-property walk flaws (CVE-2026-125116 through CVE-2026-125120):
    • sanitizeFilter bypasses (CVE-2026-125120 CVSS 9.8 Critical and CVE-2026-125119 CVSS 7.5 High): countDocuments() never ran sanitizeFilter on its query filter (CVE-2026-125120), and NativeConnection#createClient() moved { sanitizeFilter: true } from Connection.options into Connection.config while Query#_castConditions() checked only Connection.options (CVE-2026-125119), leaving connection-level sanitizeFilter ineffective against { $ne: null } authentication bypasses.
    • Inherited-property walk and prototype pollution (CVE-2026-125117 CVSS 8.2 High, CVE-2026-125116, and CVE-2026-125118): init() (document hydration), $__set (dotted path assignment), and utils.mergeClone (findOneAndReplace() and chained updates) traversed into inherited prototype methods without Object.hasOwn() checks. Passing {"meta.toString.call": 1} to new Model(req.body) on a Mixed field or {"toString": {"call": 1}} to findOneAndReplace() overwrote Object.prototype.toString.call, causing every subsequent Mongoose query in the Node.js process to fail with TypeError: _toString.call is not a function (CVE-2026-125117). Meanwhile, Schema.prototype.virtual() lacked the specialProperties guard from CVE-2022-2564 (CVE-2026-125118), and discriminator lookups resolved __t: 'constructor' to Object (CVE-2026-125116).
  3. Directus < 12.1.0 WebSocket accountability: null admin escalation (CVE-2026-126539 / GHSA-97xr-jchp-xm3c, CVSS v4.0 9.2 Critical / v3.1 8.1 High): In Directus, accountability: null signifies an internal system call that bypasses all permission checks, whereas an unauthenticated user has { role: null, user: null, admin: false, app: false }. On WebSocket connections configured in public auth mode, sending an invalid access token caused handleAuthRequest()’s catch block to set client.accountability = null, giving any unauthenticated caller full read, create, update, and delete privileges over all user-defined collections.
  4. AstroBlocks < 3.4.0 (CVE-2026-64682, CVSS 9.8), Waline <= 3.15.2 (CVE-2026-64670 CVSS 9.3, CVE-2026-64671), Mapbox node-fontnik < 0.7.7 (CVE-2026-63660, CVSS 8.1), fast-xml-parser < 5.12.0 (CVE-2026-126066), and Auth0 RAG / Management SDKs (CVE-2026-107372, CVE-2026-108167, CVE-2026-126128, CVE-2026-126129): AstroBlocks documented ASTRO_BLOCKS_JWT_SECRET in its README while reading CMS_JWT_SECRET in code and falling back to 'cms-jwt-secret-change-me'; node-fontnik overflowed a 32-bit unsigned int when multiplying buffered_width * buffered_height on a 680-byte font; and auth0-ai-js / auth0-ai-python FGA retrievers deduplicated authorization checks by (object, relation) while dropping the user and context fields, leaking documents denied by Fine-Grained Authorization into RAG prompts.

What to do now: Upgrade react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack to 19.0.9, 19.1.10, 19.2.9, or 19.3.1; mongoose to >= 9.11.4 (9.12.1 current), >= 8.24.7 (8.24.8), >= 7.8.13, or >= 6.13.12; Directus to >= 12.1.0; astro-blocks to >= 3.4.0; fontnik to >= 0.7.7; and fast-xml-parser to >= 5.12.0.

Affected packages and components

EcosystemPackageCVE / GHSASeverityAffected versionsFixed version
npmreact-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopackCVE-2026-126187 (GHSA-xqc2-xf4c-x3h3)CVSS v4.0 9.5 Critical>= 19.0.0, < 19.0.9; >= 19.1.0, < 19.1.10; >= 19.2.0, < 19.2.9; = 19.3.019.0.9, 19.1.10, 19.2.9, 19.3.1
npmmongooseCVE-2026-125120 (GHSA-pcrw-h46h-c93h), CVE-2026-125119 (GHSA-gg4r-jv3p-qx3c)CVSS 9.8 Critical / 7.5 High< 6.13.12, >= 7.0.0, < 7.8.13, >= 8.0.0, < 8.24.7, >= 9.0.0, < 9.11.46.13.12, 7.8.13, 8.24.7 (8.24.8), 9.11.4 (9.12.1)
npmmongooseCVE-2026-125117 (GHSA-8332-j7wj-wjw4), CVE-2026-125116 (GHSA-wr5m-5jph-8m96), CVE-2026-125118 (GHSA-6972-9mcm-vhwj)CVSS 8.2 High / 6.5 Medium / 4.8 Medium< 6.13.12, >= 7.0.0, < 7.8.13, >= 8.0.0, < 8.24.7, >= 9.0.0, < 9.11.46.13.12, 7.8.13, 8.24.7, 9.11.4
npm / Dockerdirectus (@directus/api)CVE-2026-126539 (GHSA-97xr-jchp-xm3c)CVSS v4.0 9.2 Critical (v3.1 8.1 High)< 12.1.012.1.0
npmastro-blocks (NauelG/astro-blocks)CVE-2026-64682 (GHSA-mfcg-m7j5-7v72)CVSS 9.8 Critical< 3.4.0 (0.3.0 to 3.3.2)3.4.0
npm@waline/client (walinejs/waline)CVE-2026-64670 (GHSA-crj3-q72p-ggqm), CVE-2026-64671CVSS 9.3 Critical / 7.2 High<= 3.15.2Sanitize orig before marked() in utils/markdown.ts
npmfontnik (mapbox/node-fontnik)CVE-2026-63660 (GHSA-cfm6-c7rv-58xj)CVSS 8.1 High< 0.7.70.7.7
npmfast-xml-parserCVE-2026-126066 (GHSA-474x-hrwr-fgx4)Low (ReDoS / CPU DoS)<= 5.11.25.12.0
npm / PyPI / NuGet@auth0/ai, auth0-ai, auth0, Auth0.AspNetCore.AuthenticationCVE-2026-107372, CVE-2026-108167, CVE-2026-126128, CVE-2026-126129High / MediumPrior to Nov 2026 Okta/Auth0 SDK patchesLatest @auth0/ai, auth0-ai, auth0, and Auth0.AspNetCore.Authentication releases

Technical analysis

1. React Server Components 19.3.1 (CVE-2026-126187 / GHSA-xqc2-xf4c-x3h3): detached ArrayBuffer stream desynchronization and Flight RESPONSE_SYMBOL hardening

In React 19’s Flight protocol (packages/react-server/src/ReactFlightServer.js and ReactServerStreamConfig*.js), binary typed arrays (Uint8Array, Float32Array, Node Buffer, etc.) are serialized as length-prefixed binary chunks (<id>:<tag><hexByteLength>,<rawBytes>). Small chunks (<= VIEW_SIZE, 4,096 bytes) are copied into React’s internal currentView ring buffer, whereas chunks larger than 4,096 bytes are passed directly to the destination byte stream (controller.enqueue(chunk)).

Under the WHATWG Streams specification, enqueuing a Uint8Array into a readable byte stream transfers and detaches the entire underlying ArrayBuffer. In ReactServerStreamConfigNode.js, ReactServerStreamConfigEdge.js, and ReactServerStreamConfigBrowser.js prior to commit 0c9913ae8728, typedArrayToBinaryChunk() returned new Uint8Array(content.buffer, content.byteOffset, content.byteLength) without slicing partial views, and writeViewChunk() / writeChunk() silently ignored zero-length chunks:

// packages/react-server/src/ReactServerStreamConfigEdge.js (vulnerable < 19.3.1)
export function writeChunk(
  destination: Destination,
  chunk: PrecomputedChunk | Chunk | BinaryChunk,
): void {
  if (chunk.byteLength === 0) {
    return;
  }
  ...

When a server component or action response transported two typed arrays backed by the same ArrayBuffer (for example two subarray() slices of a shared buffer, or two views over the same ArrayBuffer where at least one exceeded 4,096 bytes) alongside an attacker-controlled string or buffer:

  1. Enqueuing the first large view detached the shared ArrayBuffer, turning the second view’s byteLength into 0 before its writeChunk() call ran.
  2. When React serialized the second view, it emitted the chunk header using the pre-detachment length, then called writeChunk() on the now-detached view. Because chunk.byteLength === 0, writeChunk() returned immediately without writing any payload bytes.
  3. The Flight stream reader consumed the next N bytes from subsequent chunks (including attacker-controlled strings or buffers in the same response) as the body of the binary chunk, and then began parsing the middle of the attacker-controlled value as raw top-level Flight protocol lines (id:model).

To prevent stream framing injection and harden the Flight deserialization surface on both client and server, commit 0c9913ae8728 makes four coordinated changes:

--- a/packages/react-client/src/ReactFlightClient.js
+++ b/packages/react-client/src/ReactFlightClient.js
@@ -173,6 +173,9 @@ const __PROTO__ = '__proto__';
+type RESPONSE_SYMBOL_TYPE = 'RESPONSE_SYMBOL'; // Fake symbol type.
+const RESPONSE_SYMBOL: RESPONSE_SYMBOL_TYPE = Symbol() as any;
...
@@ -866,7 +869,7 @@ function createResolvedModelChunk<T>(
-  return new ReactPromise(RESOLVED_MODEL, value, response);
+  return new ReactPromise(RESOLVED_MODEL, value, {[RESPONSE_SYMBOL]: response});
 }
...
@@ -2071,6 +2076,15 @@ function loadServerReference<A: Iterable<any>, T>(
+  if (key === 'then') {
+    return null as any;
+  }
+  const id = metaData.id;
+  if (typeof id !== 'string') {
+    return null as any;
+  }
  1. Detached and partial ArrayBuffer checks (ReactServerStreamConfig*.js): typedArrayToBinaryChunk() now copies (view.slice()) any view larger than VIEW_SIZE that does not span its entire ArrayBuffer (byteOffset !== 0 || byteLength !== buffer.byteLength), is backed by a resizable buffer, or runs in an environment without ArrayBuffer.prototype.detached. In writeChunk(), if chunk.byteLength === 0 and chunk.buffer.detached is true, React throws Error('Cannot transport a detached buffer...') instead of emitting a truncated frame.
  2. RESPONSE_SYMBOL and loadServerReference hardening (ReactFlightClient.js): Previously, ResolvedModelChunk stored the internal Response object (which holds _bundlerConfig and _serverReferenceConfig) directly on chunk.reason, where a crafted model reference could reach it. React now wraps reason in {[RESPONSE_SYMBOL]: response}, rejects key === 'then' in loadServerReference() and createModel(), and verifies bound instanceof ReactPromise before awaiting metaData.bound.
  3. Namespace-separated BackingFormData (ReactFlightReplyBackingFormData.js and ReactFlightReplyServer.js): On the Server Actions reply path, stream chunks now use a dedicated prefix + 'S' + id field namespace, and BackingFormData stores strings (getBackingString), streams (getStreamChunks), referenced FormData (consumeBackingEntries), and Blobs (getBackingBlob) in separate maps so a string field can never masquerade as a Blob or stream chunk.

2. Mongoose 9.11.4 / 8.24.7 (CVE-2026-125120, CVE-2026-125119, CVE-2026-125117, CVE-2026-125116, CVE-2026-125118): sanitizeFilter omissions and Object.prototype.toString corruption

Mongoose’s five 10 November advisories fall into two classes:

  1. sanitizeFilter skipped on countDocuments() (CVE-2026-125120, CVSS 9.8 Critical, commit b5003d3915db) and on connection-level options (CVE-2026-125119, CVSS 7.5 High, commit 4bb659478be2): When developers enable sanitizeFilter to neutralize NoSQL operator objects (such as { password: { $ne: null } }) by wrapping them in $eq, Query.prototype.countDocuments did not invoke sanitizeFilter(this._conditions). Even worse, when sanitizeFilter: true was passed to mongoose.connect(uri, { sanitizeFilter: true }) or mongoose.createConnection(uri, { sanitizeFilter: true }), NativeConnection#createClient() (lib/drivers/node-mongodb-native/connection.js:270-272) moved options.sanitizeFilter into this.config.sanitizeFilter and deleted options.sanitizeFilter, whereas Query#_castConditions() (lib/query.js:2413-2423) checked this.model.db.options?.sanitizeFilter and never this.model.db.config.sanitizeFilter.
  2. Walking into inherited properties during hydration, $__set, and mergeClone (CVE-2026-125117, CVSS 8.2 High, commit 18b5513dd463): Although Mongoose blocked __proto__, constructor, and prototype, three core traversal functions read doc[i] or to[key] without checking Object.hasOwn():
    • In Document.prototype.$__set (called by new Model(req.body) and doc.set()), setting a dotted path inside any Schema.Types.Mixed ({}) field such as new Item(JSON.parse('{"meta.toString.call": 1}')) resolved meta.toString to the inherited Object.prototype.toString function and assigned .call = 1 directly onto that shared global function.
    • In utils.mergeClone (called by Model.findOneAndReplace(filter, req.body)), passing {"toString": {"call": 1}} recursed into to['toString'] (Object.prototype.toString) and overwrote .call = 1.
    • Once Object.prototype.toString.call is overwritten with a non-function, every subsequent Mongoose query across the entire Node.js process throws TypeError: _toString.call is not a function until the server restarts. Similarly, on a subdocument with strict: false, calling doc.set('profile.$__schema.paths.email.validators', []) mutated the shared schema validator array in memory for all documents (CVE-2026-125117).

3. Directus < 12.1.0 (CVE-2026-126539 / GHSA-97xr-jchp-xm3c): failed WebSocket auth resets accountability to null (admin)

In Directus, permissions on database operations are gated by the Accountability object passed into services:

  • An unauthenticated (public) user carries { role: null, user: null, admin: false, app: false }.
  • Passing accountability: null means no permission enforcement (internal system/admin context).

In api/src/websocket/controllers/base.ts prior to v12.1.0 (commit 8d4cd86783bc), when a WebSocket endpoint operated in public authentication mode and a client sent { "type": "auth", "access_token": "invalid" }, handleAuthRequest() caught the authentication error and assigned accountability = null instead of resetting it with createDefaultAccountability():

--- a/api/src/websocket/controllers/base.ts
+++ b/api/src/websocket/controllers/base.ts
@@ -381,8 +376,8 @@ export default abstract class SocketController {
 		} catch (err: any) {
-			client.accountability = null;
+			client.accountability = createDefaultAccountability(this.accountabilityOverrides);
 			client.expires_at = null;

Any subsequent CRUD message (items read, create, update, or delete) sent over that WebSocket connection ran with client.accountability === null, bypassing all collection permissions.

4. AstroBlocks 3.4.0 (CVE-2026-64682), Mapbox node-fontnik 0.7.7 (CVE-2026-63660), Waline (CVE-2026-64670), and Auth0 AI / Node SDKs (CVE-2026-107372, CVE-2026-108167, CVE-2026-126128, CVE-2026-126129)

  • AstroBlocks < 3.4.0 JWT secret env-var mismatch (CVE-2026-64682 / GHSA-mfcg-m7j5-7v72, CVSS 9.8 Critical, commit fd83bf0b37a7): All documentation instructed users to set ASTRO_BLOCKS_JWT_SECRET, while the runtime code read process.env.CMS_JWT_SECRET || 'cms-jwt-secret-change-me'. Even deployments that configured ASTRO_BLOCKS_JWT_SECRET silently signed and verified admin tokens with the public fallback string 'cms-jwt-secret-change-me', allowing anyone to mint a JWT with role: "owner".
  • Mapbox node-fontnik < 0.7.7 32-bit SDF bitmap integer overflow (CVE-2026-63660 / GHSA-cfm6-c7rv-58xj, CVSS 8.1 High, PR #202): In include/mapbox/glyph_foundry_impl.hpp, RenderSDF() calculated the SDF bitmap allocation size as unsigned int buffered_width * buffered_height from unvalidated font bounding-box metrics. A 680-byte font file with a $65536 \times 65536$ buffered glyph wrapped the 32-bit product to 0, allocating a zero-byte buffer and writing one byte per pixel across the heap. Version 0.7.7 caps glyph dimensions at 256px and widens buffer indexing to size_t.
  • Auth0 AI FGA Retriever context conflation (CVE-2026-107372 in @auth0/ai and CVE-2026-108167 in auth0-ai) and Node/ASP.NET SDKs (CVE-2026-126128, CVE-2026-126129): When filtering RAG documents through Auth0 Fine-Grained Authorization (FGA), the JS and Python FGA retrievers keyed batch check results without distinguishing different user, relation, or conditional context values, causing documents denied by FGA to be included in the LLM prompt context.

Detection and remediation

# 1. Check npm lockfiles and dependency trees for React Server Components, Mongoose, Directus, AstroBlocks, Waline, fontnik, fast-xml-parser, and Auth0 SDKs
npm ls react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack mongoose directus @directus/api astro-blocks @waline/client fontnik fast-xml-parser @auth0/ai auth0 2>/dev/null || true

rg -n '"(react-server-dom-webpack|react-server-dom-parcel|react-server-dom-turbopack|mongoose|directus|@directus/api|astro-blocks|@waline/client|fontnik|fast-xml-parser|@auth0/ai|auth0)"' \
  package.json package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null

# 2. Audit Mongoose codebases for connection-level sanitizeFilter, countDocuments with req.body/req.query, and schema.virtual() with dynamic paths
rg -n 'sanitizeFilter|countDocuments\s*\(|findOneAndReplace\s*\(|\.virtual\s*\(' --glob '*.{js,ts,mjs,cjs}' 2>/dev/null
  1. Upgrade React Server Components packages immediately to 19.0.9, 19.1.10, 19.2.9, or 19.3.1: Any application using Next.js, Parcel, Webpack, or Turbopack with React 19 Server Components or Server Actions should update react-server-dom-* to the patched release for its minor line.
  2. Upgrade Mongoose to >= 9.11.4 (9.12.1), >= 8.24.7 (8.24.8), >= 7.8.13, or >= 6.13.12: If you cannot upgrade immediately, set mongoose.set('sanitizeFilter', true) globally rather than relying on connection-level { sanitizeFilter: true }, and add a pre('countDocuments') plugin that calls mongoose.sanitizeFilter(this.getFilter()).
  3. Upgrade Directus to >= 12.1.0 and AstroBlocks to >= 3.4.0: On AstroBlocks instances that ran < 3.4.0, rotate ASTRO_BLOCKS_JWT_SECRET, invalidate all existing session tokens, and audit CMS users and content for unauthorized owner actions.

Timeline

  • 2026-11-04 to 2026-11-09: fast-xml-parser releases 5.12.0 (CVE-2026-126066), and Mongoose tags 6.13.11/6.13.12, 7.8.12/7.8.13, 8.24.3/8.24.7, and 9.9.2/9.11.4.
  • 2026-11-10 (16:21 to 23:17 UTC): React publishes 19.0.9, 19.1.10, 19.2.9, and 19.3.1 (0c9913ae8728) and GHSA-xqc2-xf4c-x3h3 / CVE-2026-126187; GitHub and NVD publish the five Mongoose advisories (CVE-2026-125116 through CVE-2026-125120) and the four Okta/Auth0 advisories (CVE-2026-107372, CVE-2026-108167, CVE-2026-126128, CVE-2026-126129).
  • 2026-11-11 (01:17 to 05:19 UTC): NVD publishes CVE-2026-126539 (Directus < 12.1.0), CVE-2026-63660 (node-fontnik < 0.7.7), CVE-2026-64670 and CVE-2026-64671 (@waline/client <= 3.15.2), and CVE-2026-64682 (astro-blocks < 3.4.0).

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References