DEADLINE ALERT for SOC and LMT: The Law Offices of Frank R. Cruz Reminds Investors of Class Actions on Behalf of Shareholders

LOS ANGELES, July 31, 2025 (GLOBE NEWSWIRE) -- The Law Offices of Frank R. Cruz reminds investors that class action lawsuits have been filed on behalf of shareholders of the following publicly-traded companies.  Investors have until the deadlines listed below to file a lead plaintiff motion.

Investors suffering losses on their investments are encouraged to contact The Law Offices of Frank R. Cruz to discuss their legal rights in these class actions at 310-914-5007 or by email to fcruz@frankcruzlaw.com.

Sable Offshore Corp. (NYSE: SOC)
Class Period: May 19, 2025 – June 3, 2025
Lead Plaintiff Deadline: September 26, 2025

The complaint filed in this class action alleges that throughout the Class Period, Defendants made materially false and/or misleading statements, as well as failed to disclose material adverse facts about the Company’s business, operations, and prospects. Specifically, Defendants failed to disclose to investors that: (1) Defendants represented that Sable Offshore Corp. had restarted oil production off the coast of California when it had not; and (2) as a result, Defendants’ positive statements about the Company’s business, operations, and prospects were materially misleading and/or lacked a reasonable basis at all relevant times.

If you are a Sable shareholder who suffered a loss, click here to participate.

Lockheed Martin Corporation (NYSE: LMT)
Class Period: January 23, 2024 – July 21, 2025
Lead Plaintiff Deadline: September 26, 2025

The complaint filed in this class action alleges that throughout the Class Period, Defendants made materially false and/or misleading statements, as well as failed to disclose material adverse facts about the Company’s business, operations, and prospects. Specifically, Defendants failed to disclose to investors: (1) that Lockheed Martin lacked effective internal controls regarding its purportedly risk adjusted contracts including the reporting of its risk adjusted profit booking rate; (2) that Lockheed Martin lacked effective procedures to perform reasonably accurate comprehensive reviews of program requirements, technical complexities, schedule, and risks; (3) that Lockheed Martin overstated its ability to deliver on its contract commitments in terms of cost, quality and schedule; (4) that, as a result, the Company was reasonably likely to report significant losses; and (5) that, as a result of the foregoing, Defendants’ positive statements about the Company’s business, operations, and prospects were materially misleading and/or lacked a reasonable basis.

If you are a Lockheed shareholder who suffered a loss, click here to participate.

Follow us for updates on Twitter: twitter.com/FRC_LAW.

To be a member of these class actions, you need not take any action at this time; you may retain counsel of your choice or take no action and remain an absent member of the class action. If you wish to learn more about these class actions, or if you have any questions concerning this announcement or your rights or interests with respect to these matters, please contact Frank R. Cruz, of The Law Offices of Frank R. Cruz, 1999 Avenue of the Stars, Suite 1100, Los Angeles, California 90067 at 310-914-5007, by email to info@frankcruzlaw.com, or visit our website at www.frankcruzlaw.com.   If you inquire by email please include your mailing address, telephone number, and number of shares purchased.

This press release may be considered Attorney Advertising in some jurisdictions under the applicable law and ethical rules.

Contacts

The Law Offices of Frank R. Cruz, Los Angeles
Frank R. Cruz, 310-914-5007
fcruz@frankcruzlaw.com
www.frankcruzlaw.com

Legal Disclaimer:

EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.