CVE-2026-57912
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 · uneditedJohnson & Johnson Campus Recruiting before 2025-10-31 allows viewing of data provided by recruited students, and notes entered about students by interviewers.
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 · moderate confidenceThe Johnson & Johnson Campus Recruiting system had an improper access control vulnerability that allowed unauthorized users to view sensitive student recruitment data and confidential interviewer notes without authentication. The CVSS 7.5 indicates network-exploitable access with low complexity and no authentication required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Johnson & Johnson Campus Recruiting system deploymentInventory your environment for any instances of the Johnson & Johnson Campus Recruiting web application. Search for related application names, hostnames, or services that may indicate this system is in use.Affected if The system is present in your environment and handles student recruitment data.
-
Verify network exposure of recruitment portalsScan your external and internal networks for web interfaces related to campus recruiting. Check firewall rules, load balancers, and proxy configurations to determine if these portals are accessible from untrusted networks.Affected if The recruiting system is exposed to the internet or untrusted internal networks without proper network segmentation.
-
Test authentication requirements on data endpointsAttempt to access common recruitment data URLs without providing credentials. Check if endpoints for student profiles, application data, and interviewer notes are reachable without a login session or API token.Affected if Sensitive recruitment data endpoints are accessible without any authentication token or session.
-
Inspect access control configurationReview the application configuration files, web.xml, or equivalent access control settings to verify role-based access controls are enforced. Look for missing authorization checks on data retrieval functions.Affected if The application lacks proper authorization checks or has misconfigured access control rules that permit unauthenticated data access.
-
Check for indicators of prior unauthorized accessReview application logs for requests to recruitment data endpoints from unauthenticated IP addresses, unusual access patterns, or requests for student notes without valid session tokens.Affected if Log evidence shows unauthenticated requests successfully accessed sensitive recruitment data.
Your environment is affected if the Johnson & Johnson Campus Recruiting system is deployed and sensitive student data or interviewer notes can be accessed without authentication from the network where the exploit is launched.
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.
From vendor dataEnsure the vendor patch or configuration fix released before 2025-10-31 is applied, and implement proper role-based access controls to ensure only authorized personnel can view student data and interviewer notes.
- Consultation5.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,360.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57912 — 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-2026-57912 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