Comparison Overview
African Union Development Agency-NEPAD

African Union Development Agency-NEPAD
230 15th Road, Johannesburg, 1685, ZA
Last Update: 01/04/2026
At the June 2018 AU Assembly a decision was taken to transform the NEPAD Planning and Coordination Agency into the African Union Development Agency-NEPAD (AUDA-NEPAD). The establishment of AUDA-NEPAD is part of the global reforms geared at improving the Union’s impact a...

Boys & Girls Clubs of America
1275 Peachtree St NE, Atlanta, Georgia, US
Last Update: 01/04/2026
Boys & Girls Clubs of America does whatever it takes for America’s youth to have great futures. As the nation's premier (nonprofit) youth development organization, our programs, training and services support millions of kids and teens every year. We hire employees who ...
Compliance Ranges Comparison

African Union Development Agency-NEPAD







Boys & Girls Clubs of America






Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for African Union Development Agency-NEPAD in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Boys & Girls Clubs of America in 2026.
Incident History - African Union Development Agency-NEPAD (X = Date, Y = Severity)
African Union Development Agency-NEPAD cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Boys & Girls Clubs of America (X = Date, Y = Severity)
Boys & Girls Clubs of America cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

African Union Development Agency-NEPAD

Boys & Girls Clubs of America
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.