Comparison Overview
U.S. DOGE Service

U.S. DOGE Service
725 17th St NW, Washington, DC, US, 20006
Last Update: 02/04/2026
*U.S. DOGE Service operated under the name U.S. Digital Service prior to January 20, 2025. The U.S. DOGE Service (USDS) is a group of mission-driven professionals passionate about delivering better government services to the public. Millions of people interact with go...

USDA
1400 Independence Ave, Washington, 20250, US
Last Update: 02/04/2026
The United States Department of Agriculture is the United States federal executive department responsible for developing and executing U.S. federal government policy on farming, agriculture, and food. It aims to meet the needs of farmers and ranchers, promote agricultur...
Compliance Ranges Comparison

U.S. DOGE Service







USDA






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
U.S. DOGE Service has 30.56% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for USDA in 2026.
Incident History - U.S. DOGE Service (X = Date, Y = Severity)
U.S. DOGE Service cyber incidents detection timeline including parent company and subsidiaries.
Incident History - USDA (X = Date, Y = Severity)
USDA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

U.S. DOGE Service

USDA
FAQ
Latest Global CVEs
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/handler.go sendFile handler opened files using a cleaned path but derived the authorization filename from raw req.URL.Path, so a trailing slash could bypass .goshs ACL-file protection and block-list checks. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/updown.go multipart upload handler split part.FileName() on / but did not reject .., allowing an unauthenticated upload with filename .. to create a file outside the served tree. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.4, the httpserver/server.go wdGuard handled WebDAV MOVE as a write-only method and did not enforce --no-delete, allowing WebDAV clients to delete or overwrite files via MOVE with Overwrite: T. This issue is fixed in version 2.1.4.
goshs is a feature-rich single-binary file server for red teamers and developers. From 2.1.3 until 2.1.4, the sftpserver/sftpserver.go password handler used Username != "" && Password != "", so running goshs with -b 'admin:' -sftp and no -fkf left both SFTP authentication handlers unset and allowed unauthenticated file access. This issue is fixed in version 2.1.4.
Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpPostRequestEncoder constructs multipart HTTP request bodies by directly concatenating user-supplied filenames and field names into Content-Disposition MIME headers without validating or sanitizing CRLF characters (\r\n). Since MIME headers are delimited by CRLF, an attacker who controls the filename can inject arbitrary MIME headers into the multipart body part. The root cause is that neither the encoder nor the FileUpload implementations' setFilename() methods, which only check for null, neutralize CRLF characters before the filename is embedded into the header. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.