Comparison Overview
Navy Region Japan Fleet and Family Readiness (FFR)

Navy Region Japan Fleet and Family Readiness (FFR)
CFA Yokosuka, JP
Last Update: 21/06/2026
OUR VISION Deliver dynamic, innovative, and integrated programs and services that inspire Sailors and Navy families to thrive throughout their military life cycle. OUR CORE ATTRIBUTES Service, Respect, Transparency, Accountability, Integrity, Dedication OUR MISSION Fl...

Israel Defense Forces
1 HaKirya, Tel Aviv, 6473209, IL
Last Update: 04/04/2026
The Israel Defense Forces (IDF) is the military of the State of Israel, responsible for the nation's defense and security. Founded in 1948, the IDF ranks among the most battle-tested armed forces in the world, having had to defend the country in six major wars. At the...
Compliance Ranges Comparison

Navy Region Japan Fleet and Family Readiness (FFR)







Israel Defense Forces






Benchmark & Cyber Underwriting Signals
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for Navy Region Japan Fleet and Family Readiness (FFR) in 2026.
Incidents vs Armed Forces Industry Avg (This Year)
Israel Defense Forces has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Navy Region Japan Fleet and Family Readiness (FFR) (X = Date, Y = Severity)
Navy Region Japan Fleet and Family Readiness (FFR) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Israel Defense Forces (X = Date, Y = Severity)
Israel Defense Forces cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Navy Region Japan Fleet and Family Readiness (FFR)

Israel Defense Forces
FAQ
Latest Global CVEs
GNU Savannah Administration Savane through 3.17 uses untrusted data as part of authorization.
- https://cgit.git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/file.php?h=release-3.17#n113
- https://cgit.git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/file.php?h=release-3.17#n123
- https://news.ycombinator.com/item?id=48605220
- https://www.fsf.org/news/statement-regarding-gnu-savannah-security-reports
- https://www.hacktron.ai
- https://www.mallory.ai/stories/019ee445-bdd4-7775-93b5-a8faaf5c2eb7
AVideo TopMenu plugin through version 26.0 contains a stored cross-site scripting vulnerability in menu item rendering due to missing output encoding of icon classes, URLs, and text labels. Attackers can inject malicious JavaScript through unescaped menu item fields that execute for all site visitors, potentially stealing session cookies or performing unauthorized actions.
AVideo through version 25.0 contains an authentication bypass vulnerability in the decryptMessage.json.php endpoint that allows unauthenticated users to decrypt PGP messages. Remote attackers can submit private keys, ciphertext, and passphrases to perform server-side decryption without credentials, exposing key material to logs and enabling resource exhaustion attacks.
AVideo through 29.0 contains an authorization bypass vulnerability in the Meet plugin's uploadRecordedVideo.json.php endpoint that derives the target users_id from the uploaded filename without verification. An attacker with knowledge of the Meet shared secret can craft a malicious file upload with a filename containing an arbitrary users_id to invoke passwordless User->login() and establish an authenticated session as any user including admin. Attackers can obtain the Meet shared secret through path-traversal vulnerabilities or timing attacks against checkToken.json.php, then POST a crafted file to uploadRecordedVideo.json.php with a filename like '1-anything.mp4' to hijack admin sessions and gain full account takeover.
AVideo through version 27.0 contains a server-side request forgery vulnerability in plugin/Live/test.php that allows authenticated administrators to read arbitrary URLs via the statsURL parameter, which lacks isSSRFSafeURL() validation and accepts requests to private IP ranges and cloud metadata endpoints. Attackers can exploit this by crafting requests to internal services, cloud metadata endpoints like 169.254.169.254, and localhost to retrieve sensitive information including IAM credentials, internal service responses, and network configuration details.