Comparison Overview
Office of the Special Envoy for Critical and Emerging Technology
Office of the Special Envoy for Critical and Emerging Technology
2201 C Street NW, Washington, 20520, US
Last Update: 04/04/2026
The Office of the Special Envoy for Critical and Emerging Technology (S/TECH) is the U.S. Department of State's focal point for strategic competition; for cooperation with allies and partners on critical and emerging technologies; and leads the planning for integrated i...
City of Houston
901 Bagby, Houston, 77002, US
Last Update: 02/04/2026
Home to a respected and energetic cultural arts scene, celebrated restaurants featuring flavors from 35 countries, world-renowned theater groups and the brains behind U.S. space exploration, Houston is a diverse metropolis brimming with personality. With nearly 21,0...
Compliance Ranges Comparison
Office of the Special Envoy for Critical and Emerging Technology
City of Houston
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Office of the Special Envoy for Critical and Emerging Technology in 2026.
Incidents vs Government Administration Industry Avg (This Year)
City of Houston has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Office of the Special Envoy for Critical and Emerging Technology (X = Date, Y = Severity)
Office of the Special Envoy for Critical and Emerging Technology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - City of Houston (X = Date, Y = Severity)
City of Houston cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Office of the Special Envoy for Critical and Emerging Technology
City of Houston
FAQ
Latest Global CVEs
ClipBucket V5's web installer fails to properly validate or escape the php_cli_filepath parameter before passing it to shell execution. Unauthenticated attackers can submit a crafted POST request to the installer with a malicious php_cli_filepath value to execute arbitrary commands as the web server user.
- https://github.com/MacWarrior/clipbucket-v5
- https://github.com/MacWarrior/clipbucket-v5/blob/5.5.3-%23153/upload/cb_install/functions_install.php
- https://github.com/MacWarrior/clipbucket-v5/blob/5.5.3-%23153/upload/includes/classes/system.class.php
- https://github.com/MacWarrior/clipbucket-v5/commit/36e7c6cfd81f62a091d2aeef96a8fc2fc2d85dc4
- https://www.vulncheck.com/advisories/clipbucket-v5-5.5.1-through-5.5.3-153-os-command-injection-via-installer-php-cli-filepath-parameter
A vulnerability was detected in TOTOLINK N600R 4.3.0cu.7647_B20210106. The impacted element is the function getCurrentTime of the file /cgi-bin/cstecgi.cgi. Performing a manipulation of the argument ntp_server results in command injection. The attack can be initiated remotely. The exploit is now public and may be used.
- https://github.com/dxz0069/WAVLINK-WN530H4-Command-Injection-in-set_add_routing/blob/main/TOTOLINK_N600R_cstecgi_Time_WiFi_Service_popen_Command_Injection.md
- https://vuldb.com/cve/CVE-2026-79912
- https://vuldb.com/submit/881261
- https://vuldb.com/vuln/395062
- https://vuldb.com/vuln/395062/cti
- https://www.totolink.net/
A security vulnerability has been detected in TOTOLINK N600R 4.3.0cu.7647_B20210106. The affected element is the function setSystemConfig of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Such manipulation of the argument Hostname leads to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used.
- https://github.com/dxz0069/WAVLINK-WN530H4-Command-Injection-in-set_add_routing/blob/main/TOTOLINK_N600R_cstecgi_strcpy_sprintf_Multi_Function_Stack_Overflow.md
- https://vuldb.com/cve/CVE-2026-79911
- https://vuldb.com/submit/881258
- https://vuldb.com/vuln/395061
- https://vuldb.com/vuln/395061/cti
- https://www.totolink.net/
Doorkeeper OpenID Connect implements an OpenID Connect authentication provider for Rails applications on top of Doorkeeper. Prior to 1.10.4, the Dynamic Client Registration (DCR) endpoint persists client-supplied scopes without validating them against the server's configured scope set. Under certain conditions, this allows a self-registered client to obtain scopes beyond what the server intended to grant. In DynamicClientRegistrationController#application_params, the scopes attribute is assigned directly from params[:scope] with no validation against Doorkeeper.configuration.scopes or optional_scopes. Combined with enforce_configured_scopes being off by default and Doorkeeper's ScopeChecker prioritizing application-level scopes over server-level scopes, this creates a privilege escalation path. This issue is fixed in version 1.10.4.
Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal Drupal core allows Stored XSS. This issue affects Drupal core versions: from 0.0.0 to 10.6.13, from 11.3.0 to 11.3.14, from 11.4.0 to 11.4.4, from 0.0.0 to 11.0.*, from 0.0.0 to 11.1.*, from 0.0.0 to 11.2.*.