# FirstNet Security Block: Context Registered Broadcast Receivers missing Export flags in Zoom SDK

**URL:** <https://devforum.zoom.us/t/firstnet-security-block-context-registered-broadcast-receivers-missing-export-flags-in-zoom-sdk/148159>\
**Category:** Android\
**Tags:** video-sdk\
**Created:** [November 20, 2026, 6:54am UTC](https://devforum.zoom.us/t/firstnet-security-block-context-registered-broadcast-receivers-missing-export-flags-in-zoom-sdk/148159 "2026-11-20T06:54:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kiran\_xcube](https://avatars.discourse-cdn.com/v4/letter/k/22d042/32.png) [@kiran\_xcube](https://devforum.zoom.us/u/kiran_xcube)\
**Post date:** [November 20, 2026, 6:54am UTC](https://devforum.zoom.us/t/firstnet-security-block-context-registered-broadcast-receivers-missing-export-flags-in-zoom-sdk/148159/1 "2026-11-20T06:54:50Z")

</div>

**Description:**  
Hi Zoom Support Team,

During our recent NowSecure security scan for FirstNet app approval, the scan flagged a Medium-severity vulnerability originating inside the Zoom SDK. This finding is currently causing a conditional block on our FirstNet approval.  
Vulnerability: Context Registered Broadcast Receivers Not Protected with Permissions

**Affected Zoom SDK Classes:**

- us.zoom.libtools.utils
- us.zoom.hybrid (Method: onCreate)

**Technical Details:**

Present we are using Zoom Android Meeting SDK v6.5.1.31081.

The automated security scanner identified that these specific classes within the Zoom SDK are dynamically registering Broadcast Receivers using the application context without declaring whether they are exported or not.

Starting with Android 13 (API 33) and strictly enforced in Android 14 (API 34), Android requires developers to explicitly include the RECEIVER\_EXPORTED or RECEIVER\_NOT\_EXPORTED flag when registering context receivers. Because these receivers lack export flags or explicit signature-level permissions, the scanner flags them as a vulnerability where third-party apps could potentially send unauthorized intents to them.

Because these classes are internal to the compiled Zoom SDK, we cannot add the required flags on our end.

**Request:**  
Could you please escalate this to your SDK engineering team so they can review these classes and apply the appropriate RECEIVER\_NOT\_EXPORTED or RECEIVER\_EXPORTED flags to the dynamic receiver registrations?

Please let us know if there is an existing beta build that resolves this, or when we can expect a patched version of the SDK, so we can update our FirstNet compliance documentation.
