FedEx Corporation A.I CyberSecurity Scoring
10/03/2026
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for FedEx Corporation in 2026.
No incidents recorded for FedEx Corporation in 2026.
No incidents recorded for FedEx Corporation in 2026.
FedEx connects people and possibilities through our worldwide portfolio of shipping, transportation, e-commerce and digital supply chain services. For decades, we’ve been innovating to deliver more for you. Strengthening supply chains with our global network. Simplifying logistics. Enhancing tracking and visibility. And using data from every journey to make your experience better. Our people are the foundation of our success, and FedEx has consistently ranked among the world’s most admired and trusted employers. We inspire our global workforce of more than 575,000 team members to remain absolutely, positively focused on safety, the highest ethical and professional standards, and the needs of their customers and communities. Day one: 186 deliveries. Today: About 14.5 million.
BNSF Railway operates one of the largest railroad networks in North America, with about 32,500 route miles in 28 states and three Canadian provinces. The railway is among the world's top transporters of intermodal traffic, serves more grain-producing regions than any other railroad, and transports the components of many of the products we depend on daily. BNSF Railway is an Equal Opportunity Employer Minorities/Women/Veterans/Disabled. On Feb. 12, 2010, Burlington Northern Santa Fe Corporation was acquired by Berkshire Hathaway Inc. (NYSE: BRK)
As the country's postal service and leading ecommerce delivery company, we’re committed to serving Canadians and Canadian businesses, working for the greener good, and delivering a stronger Canada. We are the only delivery organization with the network and commitment to serve all of the more than 17 million addresses across Canada. We operate the largest retail network in Canada, with almost 5,900 post offices in every corner of the country. Our nearly 68,000 employees connect us with Canadians and are proud to serve the communities where they live and work. Canadians are at the heart of everything we do. We are dedicated to meeting their rapidly evolving needs and expectations. Our purpose, A Stronger Canada – Delivered, is anchored in our commitment to provide a service all Canadians can count on; demonstrate environmental and social leadership; and create a safe and welcoming workplace for all employees. En tant que service postal et chef de file de la livraison des colis du cybercommerce au pays, nous sommes déterminés à servir la population et les entreprises d’ici, et à être porteurs d’un Canada plus fort et plus vert. Grâce à notre réseau de livraison inégalé, nous avons la responsabilité de servir plus de 17 millions d’adresses d’un océan à l’autre. Avec près de 5 900 bureaux de poste, nous exploitons le plus vaste réseau de vente au détail au pays. Nos gens – quelque 68 000 employées et employés – servent fièrement les collectivités où ils vivent et travaillent, et nous relient à la population. Les Canadiennes et les Canadiens sont au cœur de tout ce que nous faisons, et nous mettons tout en œuvre pour répondre à leurs besoins et à leurs attentes qui évoluent rapidement. Notre raison d’être, Porteurs d’un Canada plus fort, repose sur notre volonté d’offrir un service sur lequel tout le monde peut compter, de faire preuve de leadership en matière d’environnement et de responsabilité sociale, et de créer un milieu de travail sécuritaire et accueillant.
Latest updates, reports, and threat intel affecting the global network.
FedEx Corporation (NYSE:FDX) is among the 11 Best All-Time High Stocks to Buy According to Wall Street. On February 13, 2026, Stifel analyst...
Wall Street is rotating into FedEx as the logistics giant hits record highs, driven by a corporate restructuring and a planned spin-off of...
FedEx Corporation (FDX) operates a global network for express shipping, ground transportation, freight forwarding, and logistics support.
FedEx Corporation (FDX) operates a global network for express shipping, ground transportation, freight forwarding, and logistics support.
The London Company, an investment management company, released “The London Company Large Cap Strategy” fourth-quarter 2025 investor letter.
MEMPHIS, Tenn., February 12, 2026--FedEx Corp. (NYSE: FDX) today announced at its 2026 Investor Day the company's strategy to strengthen its...
FedEx Corp. announced on Wednesday FedEx Freight President and CEO William J. Logue will retire Dec. 31 due to undisclosed heath reasons.
On Dec. 1, 2025, FedEx Corporation Group Health Plan disclosed a cybersecurity incident that has potentially compromised personally...
Recognition highlights company's operational excellence and commitment to customer satisfaction.
tls_opt_dtls_peer_connection_id_value_get() in subsys/net/lib/sockets/sockets_tls.c, which handles getsockopt(SOL_TLS, TLS_DTLS_PEER_CID_VALUE), passed the caller-supplied optval directly to mbedtls_ssl_get_peer_cid() without verifying the buffer was at least MBEDTLS_SSL_CID_OUT_LEN_MAX (default 32) bytes. mbedtls_ssl_get_peer_cid() copies the peer-negotiated DTLS Connection ID (length 1..MBEDTLS_SSL_CID_OUT_LEN_MAX) into that buffer without a destination-size parameter, so a caller-supplied optlen smaller than the CID causes a write of up to 31 bytes past the buffer end. In CONFIG_USERSPACE builds the getsockopt syscall verifier (z_vrfy_zsock_getsockopt) bounce-buffers the user's optval into a kernel allocation of exactly optlen bytes (k_usermode_alloc_from_copy -> z_thread_malloc), so an unprivileged user thread that passes a small optlen on a connected DTLS socket with Connection ID enabled induces a kernel-heap buffer overflow, with the overflowing content being the remote peer's CID. The defect requires CONFIG_MBEDTLS_SSL_DTLS_CONNECTION_ID, an established DTLS session with a negotiated peer CID, and (for the kernel-crossing case) CONFIG_USERSPACE. Introduced when the TLS_DTLS_CID option was added (v3.5.0). The fix rejects callers whose optlen is below MBEDTLS_SSL_CID_OUT_LEN_MAX with -EINVAL.
react18-use is a React 19 use hook shim. Between 2026-05-19 01:07:01 and 2026-05-19 15:20:43, the default branch contained malicious commits 7b79148d1495a2505f9277da295a98cf176f4496 through 7b79148d1495a2505f9277da295a98cf176f4496 that executed remote attacker-controlled code on developer machines during `npm install`. The commits were removed by force-push, but local clones, forks, and direct-SHA URLs may still contain them, and `npm install` against an affected checkout will still execute the code today. The package was not published to npm. `src/install.js` was added and wired into the `postinstall` script. It fetched a JavaScript payload from an attacker-controlled HTTPS endpoint (configurable via an environment variable), disabled TLS verification, and evaluated the response as code with `require` available. Execution was deliberately skipped on CI and cloud/serverless environments, targeting developer workstations. The second-stage payload was attacker-hosted and cannot be reconstructed. Assume full compromise of anything reachable from a Node process with the user's permissions. Those who ran `npm install` against an affected checkout on a developer machine on or after 2026-05-19 01:07:01 should treat the machine as compromised, rotate every credential the machine could reach, audit account activity since 2026-05-19 01:07:01, and clean local clones.
The UpdateHub management subsystem (subsys/mgmt/updatehub/updatehub.c) drives every update operation through a single file-scope ctx structure that holds the CoAP block context, payload buffer, status code, socket, and a one-element poll-fd array fds[1]. Access to ctx was not serialized, and prepare_fds() wrote ctx.fds[ctx.nfds] and incremented ctx.nfds with no bounds check. Two independent paths mutate ctx concurrently: the background autohandler running on the system workqueue, and user-triggered operations reached through the updatehub run shell command, direct API calls, or — since the operations are exposed as syscalls — userspace threads. When a second flow enters prepare_fds() while ctx.nfds is already 1, the write lands one element past the array; by struct layout it overlaps the adjacent ctx.sock/ctx.nfds members. More broadly, the unsynchronized sharing lets two flows interleave connection setup and teardown, double-closing a socket descriptor or scribbling the shared buffers. The result is corruption of the update subsystem's internal state and denial of service of the firmware-update path; the out-of-bounds write is contained within the ctx structure and there is no demonstrated path to memory outside it or to code execution. Triggering requires a local actor able to invoke update operations (or, with CONFIG_USERSPACE, an unprivileged userspace thread) and to win a timing race against the background handler; remote peers cannot control the race timing. The fix serializes the entry points with a mutex and adds a bounds check to prepare_fds().
The UpdateHub over-the-air update client's start_coap_client() in subsys/mgmt/updatehub/updatehub.c leaks the CoAP/DTLS socket descriptor on its connection-setup failure paths. The shared error: cleanup gated socket closing on a ret > 0 flag, but ret was set to -1 immediately after the socket was created, so when zsock_setsockopt() (DTLS) or zsock_connect() subsequently failed the gate was false and cleanup_connection() was never called. The open descriptor in the global ctx.sock was then overwritten by the next attempt, permanently leaking it from the socket / net_context pool until reboot. The failing setup path is reached every time the OTA client tries to contact the UpdateHub server and the connection cannot be established — driven automatically by the periodic autohandler() poll (and on demand via the updatehub_probe()/updatehub_update() API or the updatehub run shell command). The DTLS handshake/connect outcome is influenceable by a network or on-path attacker who drops, resets, or otherwise disrupts traffic to the server, and also fails naturally whenever the server is unreachable. Each failed attempt permanently leaks one descriptor; once the shared socket pool is exhausted, networking degrades device-wide until the device is rebooted, a denial-of-service condition. Severity is low because the leak rate is bounded by the configured OTA poll interval (default once per 24 hours), the effect is gradual and recovered by reboot, and only builds with the UpdateHub client enabled are affected. There is no memory-corruption, information-disclosure, or authentication impact.
Certain web interface components in affected TP-Link Aginet devices do not validate and sanitize user-supplied input properly before passing it to system-level command execution functions. An authenticated adjacent attacker may inject specially crafted input to execute arbitrary operation system commands with elevated privileges. Successful exploitation may allow execution of arbitrary system commands, potentially leading to full device compromise.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.