CausewayApplication · Apache
CVE-2025-64408
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApache Causeway faces Java deserialization vulnerabilities that allow remote code execution (RCE) through user-controllable URL parameters. These vulnerabilities affect all applications using Causeway's ViewModel functionality and can be exploited by authenticated attackers to execute arbitrary code with application privileges. This issue affects all current versions. Users are recommended to upgrade to version 3.5.0, which fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Causeway contains Java deserialization vulnerabilities in its ViewModel functionality. Authenticated attackers can exploit user-controllable URL parameters to achieve remote code execution with application privileges through malicious serialized objects.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CausewayApplication
>= 2.0.0, < 3.5.0= 4.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Causeway versionCheck your project's pom.xml, build.gradle, or application startup logs for the Apache Causeway version number. Also inspect the WAR/EAR file manifest if deployed as a packaged application.Affected if The version is >= 2.0.0 and < 3.5.0, or exactly 4.0.0
-
Confirm ViewModel functionality is in useDetermine if your Causeway application exposes RESTful endpoints or any user-accessible URLs that utilize ViewModel serialization. This is typically enabled by default in web-based Causeway applications.Affected if ViewModel endpoints are accessible to authenticated users, making deserialization possible through crafted URL parameters
-
Check application deployment exposureReview network accessibility of the Causeway application. Check if it is exposed to untrusted networks or the internet, or if only trusted internal users have access.Affected if The application is network-accessible to authenticated but untrusted users who could inject malicious serialized objects
-
Verify deserialization filters are absentInspect the application's security configuration or servlet filters for custom ObjectInputStream restrictions or Java deserialization safeguards in the web.xml or equivalent configuration.Affected if No deserialization filters are configured to whitelist or restrict expected classes for ViewModel deserialization
You are affected if your Apache Causeway version falls within 2.0.0 to below 3.5.0 or equals exactly 4.0.0, and your application allows authenticated users to access ViewModel functionality over the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.5.0
Upgrade Apache Causeway to version 3.5.0 or later to receive the deserialization vulnerability fix. Prioritize patching for any internet-facing deployments using ViewModel functionality.
Apache Causeway 3.5.0
- 1. Identify the current Apache Causeway version in your project's dependency management (e.g., Maven pom.xml, Gradle build file)
- 2. Update the Causeway dependency version from your current version to version 3.5.0
- 3. Rebuild your application with the updated dependency
- 4. Run your application's test suite to verify functionality remains intact, particularly ViewModel-related features
- 5. Deploy the rebuilt application to your environment
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Causeway
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64408 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64408 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data