Okta bets on identity to control AI agents, but is identity enough?
More on identity
Other advisories
- HighCVE-2026-110856GitPython parse_actor_and_date() is vulnerable to quadratic backtracking on malformed identity lines
- Highghsa:GHSA-m64x-33q8-m5h7GitPython parse_actor_and_date() is vulnerable to quadratic backtracking on malformed identity lines
- Not ratedosv:CLEANSTART-2026-VA82083Forward-reference completion for @JsonIdentityInfo object IDs in FasterXML jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID
- Not ratedosv:CVE-2026-81039Bluetooth Host connection reservation leak when multiple connectable advertising sets share an identity
- CriticalCVE-2026-106072A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
- CriticalCVE-2026-106069A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
- CriticalCVE-2026-105483A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`). `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**.
- Not ratedosv:CLEANSTART-2026-YK30931Forward-reference completion for @JsonIdentityInfo object IDs in FasterXML jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID
Other news entries
- When an AI Agent Is the Incident, the Identity Record Is the EvidenceNewsBleepingComputer
- NCSC-2026-0448 [1.00] [H/H] Kwetsbaarheden verholpen in Oracle Fusion MiddlewareNewsNCSC-NL
- 14 ways attackers abuse cloud services to hack your enterpriseNewsCSO Online
- Close Identity Gaps in Software Development Before Unleashing AINewsDark Reading
- University of Copenhagen breach exposes data of 525,000 peopleBreachpwn.watch
- Inside the Underground Market for Know Your Client ServicesNewsBleepingComputer
- ConnectWise Cloud Backup shut down after M365 app-identity hijackBreachpwn.watch
- Watch Now: Zero Trust Strategies Summit – All Sessions Available on DemandEventSecurityWeek
ID