Comparison Overview
Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy

Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy
N/A
Last Update: 04/04/2026
Our mission is to Accelerate AI-enabled capabilities through strategic portfolio alignment while scaling Department-wide use cases that advance the agency’s core missions; advocate for program offices; lead responsible and trustworthy AI strategies; and expand public, p...

Department of Education
AU
Last Update: 01/04/2026
The Department of Education is responsible for delivering the Victorian Government’s commitment to making Victoria the Education State, where all Victorians have the best learning and development experience, regardless of their background, postcode or circumstances. Edu...
Compliance Ranges Comparison

Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy







Department of Education






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy in 2026.
Incidents vs Government Administration Industry Avg (This Year)
Department of Education has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy (X = Date, Y = Severity)
Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Department of Education (X = Date, Y = Severity)
Department of Education cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy

Department of Education
FAQ
Latest Global CVEs
Authentication bypass using an alternate path or channel in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform tampering over a network.
JLine is a Java library for handling console input. Prior to 3.30.14, 4.0.16, and 4.2.1, the JLine3 Telnet server remote-telnet module does not apply an upper bound to terminal dimensions received via the Telnet NAWS option, and TelnetIO.handleNAWS() in TelnetIO.java:856-879 reads client-supplied width and height as 16-bit unsigned integers and passes values such as 65535x65535 to setTerminalGeometry(), allowing an unauthenticated remote attacker to repeatedly alternate values and trigger continuous expensive rendering work that causes CPU exhaustion and denial of service. This issue is fixed in versions 3.30.14, 4.0.16, and 4.2.1.
- https://github.com/jline/jline3/commit/3ea9cad8699714dc072fade29d36be0d1e23d708
- https://github.com/jline/jline3/commit/733eb353dca7b0ea0252e724445b6defa29c393e
- https://github.com/jline/jline3/commit/86b7ba7801988aadb1a67555629522a71d603bd3
- https://github.com/jline/jline3/pull/2000
- https://github.com/jline/jline3/releases/tag/4.0.16
- https://github.com/jline/jline3/releases/tag/4.2.1
- https://github.com/jline/jline3/security/advisories/GHSA-2r2c-cx56-8933
JLine is a Java library for handling console input. Prior to 3.30.14, 4.0.16, and 4.2.1, the JLine3 Telnet server remote-telnet module does not limit the number of environment variables a client may inject via the Telnet NEW-ENVIRON option, and TelnetIO.readNEVariables() in TelnetIO.java:1127-1180 stores each variable pair in a HashMap held by ConnectionData, allowing an unauthenticated attacker to flood unique variable pairs before the terminating IAC SE byte and exhaust JVM heap memory with an OutOfMemoryError. This issue is fixed in versions 3.30.14, 4.0.16, and 4.2.1.
- https://github.com/jline/jline3/commit/0389f0ee6d0375901b602671ad5dafd4d1d4ee09
- https://github.com/jline/jline3/commit/4ee3a73849ffb9a85ec748e4e8cd8f6d81f84f40
- https://github.com/jline/jline3/commit/934f09e6128cee33c2b13d42b6e859c1ee2d194b
- https://github.com/jline/jline3/pull/2000
- https://github.com/jline/jline3/pull/2001
- https://github.com/jline/jline3/releases/tag/4.0.16
- https://github.com/jline/jline3/releases/tag/4.2.1
- https://github.com/jline/jline3/releases/tag/jline-3.30.14
- https://github.com/jline/jline3/security/advisories/GHSA-47qp-hqvx-6r3f
Exposure of private personal information to an unauthorized actor in Windows RDP allows an unauthorized attacker to disclose information over a network.
Feathersjs is a framework for creating web APIs and real-time applications with TypeScript or JavaScript. In 5.0.44 and earlier, the _.merge(target, source) utility exported by @feathersjs/commons recursively merges source into target by iterating Object.keys(source). When source was produced by JSON.parse and contains a __proto__, constructor, or prototype key, that key is returned as an own-enumerable property; the recursive merge then resolves target['__proto__'] to Object.prototype and writes attacker-supplied properties onto it, polluting the prototype for all plain objects in the process for the lifetime of the Node process. This issue is fixed in version 5.0.45.